My problem is my OS-X 10.6.2 system has problems with name resolution.
This only happens for names that are inside my firewall.
Safari and nslookup are fine - they always find the right "inside" name / IP address.
Most of the time, ping, dig and ssh get the wrong addresses - the IP address is coming from an outside "Domain hosting" server.
I am using a domain name that is being held by a "domain hosting" company and is not in use by any legitimate organization - it is "parked" and they want $3,500 for me to buy it. But I only use this domain name for internal use. We've been using it forever, but I never tried to buy it until about 12 months ago.
I have tried to force all may systems to only use my internal Windows DNS for ALL name resolution. It seems to be working OK for my Windows & Linux systems.
It seems like Safari & nslookup are OK - they always find the right internal name / IP.
But dig, ping & ssh start with my internal DNS server and then go someplace else for the IP address.
My OS-X server has the /etc/resolv.conf file set to the correct domain name & only my DNS server is listed.
nslookup resolves the name / IP address every time.
"dig" says "SERVFAIL: ":
[sysadmin@server ~]$ dig test1-001
; <<>> DiG 9.6.0-APPLE-P2 <<>> test1-001
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 19182
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;test1-001. IN A
;; Query time: 2 msec
;; SERVER: 192.168.123.10#53(192.168.123.10)
;; WHEN: Mon Nov 23 10:10:00 2009
;; MSG SIZE rcvd: 27
If I dig for the IP Address of test1-001:
[sysadmin@server ~]$ dig 192.68.123.180
; <<>> DiG 9.6.0-APPLE-P2 <<>> 192.68.123.180
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21327
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;192.68.123.180. IN A
;; ANSWER SECTION:
192.68.123.180. 0 IN A 208.67.219.132
;; Query time: 138 msec
;; SERVER: 192.168.123.10#53(192.168.123.10)
;; WHEN: Mon Nov 23 10:11:18 2009
;; MSG SIZE rcvd: 48
I have a Windows DNS server set up behind my firewall.
My firewall is set up with port 53 open and the DNS server has full access to the top level domain name servers.
Every Windows & Linux system inside the firewall is fine for all types of name / IP resolution.
Is something wrong on my Windows DNS server that only the Mac uncovers?
Is there a "special" OS-X file that controls name resolution for dig, ping and ssh?
This only happens for names that are inside my firewall.
Safari and nslookup are fine - they always find the right "inside" name / IP address.
Most of the time, ping, dig and ssh get the wrong addresses - the IP address is coming from an outside "Domain hosting" server.
I am using a domain name that is being held by a "domain hosting" company and is not in use by any legitimate organization - it is "parked" and they want $3,500 for me to buy it. But I only use this domain name for internal use. We've been using it forever, but I never tried to buy it until about 12 months ago.
I have tried to force all may systems to only use my internal Windows DNS for ALL name resolution. It seems to be working OK for my Windows & Linux systems.
It seems like Safari & nslookup are OK - they always find the right internal name / IP.
But dig, ping & ssh start with my internal DNS server and then go someplace else for the IP address.
My OS-X server has the /etc/resolv.conf file set to the correct domain name & only my DNS server is listed.
nslookup resolves the name / IP address every time.
"dig" says "SERVFAIL: ":
[sysadmin@server ~]$ dig test1-001
; <<>> DiG 9.6.0-APPLE-P2 <<>> test1-001
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 19182
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;test1-001. IN A
;; Query time: 2 msec
;; SERVER: 192.168.123.10#53(192.168.123.10)
;; WHEN: Mon Nov 23 10:10:00 2009
;; MSG SIZE rcvd: 27
If I dig for the IP Address of test1-001:
[sysadmin@server ~]$ dig 192.68.123.180
; <<>> DiG 9.6.0-APPLE-P2 <<>> 192.68.123.180
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21327
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;192.68.123.180. IN A
;; ANSWER SECTION:
192.68.123.180. 0 IN A 208.67.219.132
;; Query time: 138 msec
;; SERVER: 192.168.123.10#53(192.168.123.10)
;; WHEN: Mon Nov 23 10:11:18 2009
;; MSG SIZE rcvd: 48
I have a Windows DNS server set up behind my firewall.
My firewall is set up with port 53 open and the DNS server has full access to the top level domain name servers.
Every Windows & Linux system inside the firewall is fine for all types of name / IP resolution.
Is something wrong on my Windows DNS server that only the Mac uncovers?
Is there a "special" OS-X file that controls name resolution for dig, ping and ssh?
