How do I set up a reverse lookup zone in OSX Snow Leopard ServerMac and Exchange Server 2007: Entourage or wait for Snow Leopard (Mac OS X 10.6)?Reverse DNS - how to correctly configure for SMTP deliveryDNS Name lookup (was SSH) Not Working After Snow Leopard UpgradeMac Snow Leopard Server DNSHow do I set zone priority in Microsoft DNS?Many Snow Leopard Server Managed Preference settings do not take effectHow to resolve “HTTP/1.1 403 Forbidden” errors from iCal/CalDAV server after upgrade to Snow Leopard Server?DNS Forward Lookup on Windows Server 2003How to use external DNS Forwarders when Forward Lookup Zone doesn't contain requested subdomainReverse lookup SERVFAIL
Pirate democracy at its finest
What does $!# mean in Shell scripting?
128-bit unsigned integer
bash regexp matching fails in [[ ]]
Did 20% of US soldiers in Vietnam use heroin, 95% of whom quit afterwards?
What is a fully qualified name?
What does 気楽 mean when attached to ビール or お酒?
Adding edges to a TreeForm of an expression
Website returning plaintext password
Find the three digit Prime number P from the given unusual relationships
Count rotary dial pulses in a phone number (including letters)
A steel cutting sword?
Can I tell a prospective employee that everyone in the team is leaving?
Python program to find Armstrong numbers in a certain range
What was the idiom for something that we take without a doubt?
Defining the standard model of PA so that a space alien could understand
Python program to take in two strings and print the larger string
The art of clickbait captions
Should one buy new hardware after a system compromise?
Can my floppy disk still work without a shutter spring?
Why does this if-statement combining assignment and an equality check return true?
Why didn't Thanos use the Time Stone to stop the Avengers' plan?
How to cut a climbing rope?
Is the field of q-series 'dead'?
How do I set up a reverse lookup zone in OSX Snow Leopard Server
Mac and Exchange Server 2007: Entourage or wait for Snow Leopard (Mac OS X 10.6)?Reverse DNS - how to correctly configure for SMTP deliveryDNS Name lookup (was SSH) Not Working After Snow Leopard UpgradeMac Snow Leopard Server DNSHow do I set zone priority in Microsoft DNS?Many Snow Leopard Server Managed Preference settings do not take effectHow to resolve “HTTP/1.1 403 Forbidden” errors from iCal/CalDAV server after upgrade to Snow Leopard Server?DNS Forward Lookup on Windows Server 2003How to use external DNS Forwarders when Forward Lookup Zone doesn't contain requested subdomainReverse lookup SERVFAIL
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I am trying to set up Address Book server in Mac OSX Snow Leopard server. To do this, a requirement is that I have a FQDN set up with reverse lookup. I created a DNS entry on the godaddy DNS server to link to my static public IP address. How do I set up reverse lookup on my private DNS server so that it talks to the Internet DNS servers for reverse lookup?
When I use the Network Utility on the server, the FQDN I have set up resolves correctly to my static public IP address, but I cannot figure out how to get the reverse lookup to resolve correctly.
I am somewhat new to managing DNS, so this may be a simple fix, but I just can't figure out what to do.
domain-name-system mac-osx-server osx-snow-leopard
add a comment |
I am trying to set up Address Book server in Mac OSX Snow Leopard server. To do this, a requirement is that I have a FQDN set up with reverse lookup. I created a DNS entry on the godaddy DNS server to link to my static public IP address. How do I set up reverse lookup on my private DNS server so that it talks to the Internet DNS servers for reverse lookup?
When I use the Network Utility on the server, the FQDN I have set up resolves correctly to my static public IP address, but I cannot figure out how to get the reverse lookup to resolve correctly.
I am somewhat new to managing DNS, so this may be a simple fix, but I just can't figure out what to do.
domain-name-system mac-osx-server osx-snow-leopard
add a comment |
I am trying to set up Address Book server in Mac OSX Snow Leopard server. To do this, a requirement is that I have a FQDN set up with reverse lookup. I created a DNS entry on the godaddy DNS server to link to my static public IP address. How do I set up reverse lookup on my private DNS server so that it talks to the Internet DNS servers for reverse lookup?
When I use the Network Utility on the server, the FQDN I have set up resolves correctly to my static public IP address, but I cannot figure out how to get the reverse lookup to resolve correctly.
I am somewhat new to managing DNS, so this may be a simple fix, but I just can't figure out what to do.
domain-name-system mac-osx-server osx-snow-leopard
I am trying to set up Address Book server in Mac OSX Snow Leopard server. To do this, a requirement is that I have a FQDN set up with reverse lookup. I created a DNS entry on the godaddy DNS server to link to my static public IP address. How do I set up reverse lookup on my private DNS server so that it talks to the Internet DNS servers for reverse lookup?
When I use the Network Utility on the server, the FQDN I have set up resolves correctly to my static public IP address, but I cannot figure out how to get the reverse lookup to resolve correctly.
I am somewhat new to managing DNS, so this may be a simple fix, but I just can't figure out what to do.
domain-name-system mac-osx-server osx-snow-leopard
domain-name-system mac-osx-server osx-snow-leopard
edited Feb 16 '15 at 14:38
HopelessN00b
48.7k25117194
48.7k25117194
asked May 11 '11 at 18:36
adivis12adivis12
58531125
58531125
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The reverse DNS records should generally be handled by your ISP (they "own" the IP number, so the reverse DNS for it gets delegated to them). Contact your ISP's support to find out how to have them set it up.
If your server is behind an NAT (network address translation, i.e. it has a private internal address as well as its public address), you'll also need to set up internal DNS (both forward and reverse) with the internal numbers instead of the public numbers. You can do this in OS X's DNS service by creating a forward zone and machine record for your server, and it'll create the reverse info automatically.
Suppose your server's full DNS name is server.example.com, and its internal IP address is 192.168.1.5. You'd create a zone named "server.example.com." (be sure to include the trailing period), and add an entry to its Nameservers list with both the Zone and Nameserver Hostname set to "server.example.com.". Then, add a Machine (A) record to that zone, with the Machine name "server.example.com." (again, the trailing period is very important), and the IP address 192.168.1.5.
Once that's set, start the DNS service, and configure your server's network preferences to use 192.168.1.5 as its DNS server. If you have other computers on the network with manual IP setups, change them similarly. If you have a DHCP server running, set it to hand out 192.168.1.5 as the DNS server. That should do the trick.
I currently have my server named "server.local." Does this mean that I need to change the name of my server to "server.example.com?" (supposing my FQDN is example.com)
– adivis12
May 12 '11 at 19:40
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f268723%2fhow-do-i-set-up-a-reverse-lookup-zone-in-osx-snow-leopard-server%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The reverse DNS records should generally be handled by your ISP (they "own" the IP number, so the reverse DNS for it gets delegated to them). Contact your ISP's support to find out how to have them set it up.
If your server is behind an NAT (network address translation, i.e. it has a private internal address as well as its public address), you'll also need to set up internal DNS (both forward and reverse) with the internal numbers instead of the public numbers. You can do this in OS X's DNS service by creating a forward zone and machine record for your server, and it'll create the reverse info automatically.
Suppose your server's full DNS name is server.example.com, and its internal IP address is 192.168.1.5. You'd create a zone named "server.example.com." (be sure to include the trailing period), and add an entry to its Nameservers list with both the Zone and Nameserver Hostname set to "server.example.com.". Then, add a Machine (A) record to that zone, with the Machine name "server.example.com." (again, the trailing period is very important), and the IP address 192.168.1.5.
Once that's set, start the DNS service, and configure your server's network preferences to use 192.168.1.5 as its DNS server. If you have other computers on the network with manual IP setups, change them similarly. If you have a DHCP server running, set it to hand out 192.168.1.5 as the DNS server. That should do the trick.
I currently have my server named "server.local." Does this mean that I need to change the name of my server to "server.example.com?" (supposing my FQDN is example.com)
– adivis12
May 12 '11 at 19:40
add a comment |
The reverse DNS records should generally be handled by your ISP (they "own" the IP number, so the reverse DNS for it gets delegated to them). Contact your ISP's support to find out how to have them set it up.
If your server is behind an NAT (network address translation, i.e. it has a private internal address as well as its public address), you'll also need to set up internal DNS (both forward and reverse) with the internal numbers instead of the public numbers. You can do this in OS X's DNS service by creating a forward zone and machine record for your server, and it'll create the reverse info automatically.
Suppose your server's full DNS name is server.example.com, and its internal IP address is 192.168.1.5. You'd create a zone named "server.example.com." (be sure to include the trailing period), and add an entry to its Nameservers list with both the Zone and Nameserver Hostname set to "server.example.com.". Then, add a Machine (A) record to that zone, with the Machine name "server.example.com." (again, the trailing period is very important), and the IP address 192.168.1.5.
Once that's set, start the DNS service, and configure your server's network preferences to use 192.168.1.5 as its DNS server. If you have other computers on the network with manual IP setups, change them similarly. If you have a DHCP server running, set it to hand out 192.168.1.5 as the DNS server. That should do the trick.
I currently have my server named "server.local." Does this mean that I need to change the name of my server to "server.example.com?" (supposing my FQDN is example.com)
– adivis12
May 12 '11 at 19:40
add a comment |
The reverse DNS records should generally be handled by your ISP (they "own" the IP number, so the reverse DNS for it gets delegated to them). Contact your ISP's support to find out how to have them set it up.
If your server is behind an NAT (network address translation, i.e. it has a private internal address as well as its public address), you'll also need to set up internal DNS (both forward and reverse) with the internal numbers instead of the public numbers. You can do this in OS X's DNS service by creating a forward zone and machine record for your server, and it'll create the reverse info automatically.
Suppose your server's full DNS name is server.example.com, and its internal IP address is 192.168.1.5. You'd create a zone named "server.example.com." (be sure to include the trailing period), and add an entry to its Nameservers list with both the Zone and Nameserver Hostname set to "server.example.com.". Then, add a Machine (A) record to that zone, with the Machine name "server.example.com." (again, the trailing period is very important), and the IP address 192.168.1.5.
Once that's set, start the DNS service, and configure your server's network preferences to use 192.168.1.5 as its DNS server. If you have other computers on the network with manual IP setups, change them similarly. If you have a DHCP server running, set it to hand out 192.168.1.5 as the DNS server. That should do the trick.
The reverse DNS records should generally be handled by your ISP (they "own" the IP number, so the reverse DNS for it gets delegated to them). Contact your ISP's support to find out how to have them set it up.
If your server is behind an NAT (network address translation, i.e. it has a private internal address as well as its public address), you'll also need to set up internal DNS (both forward and reverse) with the internal numbers instead of the public numbers. You can do this in OS X's DNS service by creating a forward zone and machine record for your server, and it'll create the reverse info automatically.
Suppose your server's full DNS name is server.example.com, and its internal IP address is 192.168.1.5. You'd create a zone named "server.example.com." (be sure to include the trailing period), and add an entry to its Nameservers list with both the Zone and Nameserver Hostname set to "server.example.com.". Then, add a Machine (A) record to that zone, with the Machine name "server.example.com." (again, the trailing period is very important), and the IP address 192.168.1.5.
Once that's set, start the DNS service, and configure your server's network preferences to use 192.168.1.5 as its DNS server. If you have other computers on the network with manual IP setups, change them similarly. If you have a DHCP server running, set it to hand out 192.168.1.5 as the DNS server. That should do the trick.
answered May 11 '11 at 19:55
Gordon DavissonGordon Davisson
9,31622027
9,31622027
I currently have my server named "server.local." Does this mean that I need to change the name of my server to "server.example.com?" (supposing my FQDN is example.com)
– adivis12
May 12 '11 at 19:40
add a comment |
I currently have my server named "server.local." Does this mean that I need to change the name of my server to "server.example.com?" (supposing my FQDN is example.com)
– adivis12
May 12 '11 at 19:40
I currently have my server named "server.local." Does this mean that I need to change the name of my server to "server.example.com?" (supposing my FQDN is example.com)
– adivis12
May 12 '11 at 19:40
I currently have my server named "server.local." Does this mean that I need to change the name of my server to "server.example.com?" (supposing my FQDN is example.com)
– adivis12
May 12 '11 at 19:40
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f268723%2fhow-do-i-set-up-a-reverse-lookup-zone-in-osx-snow-leopard-server%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown