|Brian Stempin on 30 Dec 2007 12:49:46 -0800|
Sorry about that....fat fingers.
[macserver:~] root# nslookup 22.214.171.124
I'm guessing that 192.168.1.102 is a local DNS server that you control. If this is the case, then it probably has a specific entry for macserver.vsystems.net. Here is the answer that I get:
bstempi@dbengine01:~$ nslookup 126.96.36.199
188.8.131.52.in-addr.arpa name = c-69-139-74-31.hsd1.pa.comcast.net.
The other server is called the redqueen.v-system.net which is on a different dynamic ip
bstempi@dbengine01:~$ nslookup redqueen.v-system.net
I'm guessing that once your DNS server can't resolve the address, it never bothers to pass the request on elsewhere. This is probably due to 1 of 2 reasons:
1. Your DNS server is not set up to forward requests, or
2. Your DNS server thinks that it's authoritative.
I'm going to put my money on #2. If this is true, you can either find a way to update your local DNS server (ie, write a script of some sort to poll for the external IP and then correct your local DNS entry), or you can have your DNS server forward unresolvable requests to someone else's DNS server (ie, comcast, etc etc.).
On Dec 30, 2007 3:14 PM, Brian Stempin <firstname.lastname@example.org> wrote:
___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug