Can't Resolve Certain internet DNS names
- From: "hamm3r" <hammer@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Jul 2005 10:20:19 -0400
I posted this over in microsoft.public.windows.networking a few days ago,
but got no responses.
I hadn't realiazed there was a dedicated dns newsgroup for windows.
Hopefully someone can help me, because I cannot figure out my next
troubleshooting step.
It seems as though ~99% of our internet hosts resolve with no problem, but
there are some that will not resolve and I can't figure out why. We are
using DNS Server on Windows 2003 Server Standard with all of the lastes
service packs.
We are not using forwarders but are using the root hints servers for all
internet resolution. All DNS servers are pointing only to themselves for DNS
resolution.
******* Here is an example for a working resolution done from an external
host:
#> nslookup www.businessdirect.att.com
Server: 217.160.251.251
Address: 217.160.251.251#53
Non-authoritative answer:
www.businessdirect.att.com canonical name = cp.eia.att.com.
Name: cp.eia.att.com
Address: 192.20.5.62
*******Here is a nonworking nslookup from inside our network:
#> nslookup www.businessdirect.att.com
Server: 10.101.25.22
Address: 10.101.25.22#53
Non-authoritative answer:
www.businessdirect.att.com canonical name = cp.eia.att.com.
(It finds the canonical name but never resolves it).
*******Here is a working 'host' lookup from outside of our network:
#> host www.businessdirect.att.com
www.businessdirect.att.com is an alias for cp.eia.att.com.
cp.eia.att.com has address 192.20.5.62
*******Here is a nonworking 'host' lookup from inside our network:
#>host www.businessdirect.att.com
www.businessdirect.att.com is an alias for cp.eia.att.com.
(Again, it finds the canonical name but never resolves it)
*******Here is a working 'dig' from outside of our network:
#>dig www.businessdirect.att.com
; <<>> DiG 9.2.1 <<>> www.businessdirect.att.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15856
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.businessdirect.att.com. IN A
;; ANSWER SECTION:
www.businessdirect.att.com. 83927 IN CNAME cp.eia.att.com.
cp.eia.att.com. 0 IN A 192.20.5.62
;; Query time: 64 msec
;; SERVER: 217.160.251.251#53(217.160.251.251)
;; WHEN: Fri Jul 8 16:00:55 2005
;; MSG SIZE rcvd: 81
*******Here is a nonworking dig from inside our network:
#>dig www.businessdirect.att.com
; <<>> DiG 9.2.1 <<>> www.businessdirect.att.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34829
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.businessdirect.att.com. IN A
;; ANSWER SECTION:
www.businessdirect.att.com. 80921 IN CNAME cp.eia.att.com.
;; Query time: 1616 msec
;; SERVER: 10.101.25.22#53(10.101.25.22)
;; WHEN: Fri Jul 8 16:01:12 2005
;; MSG SIZE rcvd: 65
*******Here is a dig +trace from outside of our network:
#>dig +trace www.businessdirect.att.com
; <<>> DiG 9.2.1 <<>> +trace www.businessdirect.att.com
;; global options: printcmd
.. 52829 IN NS E.ROOT-SERVERS.NET.
.. 52829 IN NS F.ROOT-SERVERS.NET.
.. 52829 IN NS G.ROOT-SERVERS.NET.
.. 52829 IN NS H.ROOT-SERVERS.NET.
.. 52829 IN NS I.ROOT-SERVERS.NET.
.. 52829 IN NS J.ROOT-SERVERS.NET.
.. 52829 IN NS K.ROOT-SERVERS.NET.
.. 52829 IN NS L.ROOT-SERVERS.NET.
.. 52829 IN NS M.ROOT-SERVERS.NET.
.. 52829 IN NS A.ROOT-SERVERS.NET.
.. 52829 IN NS B.ROOT-SERVERS.NET.
.. 52829 IN NS C.ROOT-SERVERS.NET.
.. 52829 IN NS D.ROOT-SERVERS.NET.
;; Received 228 bytes from 217.160.251.251#53(217.160.251.251) in 1 ms
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
;; Received 500 bytes from 192.203.230.10#53(E.ROOT-SERVERS.NET) in 94 ms
att.com. 172800 IN NS algw1.att.com.
att.com. 172800 IN NS kcgw1.att.com.
att.com. 172800 IN NS kcgw2.att.com.
;; Received 152 bytes from 192.48.79.30#53(J.GTLD-SERVERS.NET) in 171 ms
www.businessdirect.att.com. 86400 IN CNAME cp.eia.att.com.
eia.att.com. 86400 IN NS alalia.att.com.
eia.att.com. 86400 IN NS kcalia.att.com.
;; Received 139 bytes from 192.128.167.77#53(algw1.att.com) in 25 ms
*******Here is a dig +trace from inside our network:
#>dig +trace www.businessdirect.att.com
; <<>> DiG 9.2.1 <<>> +trace www.businessdirect.att.com
;; global options: printcmd
.. 43740 IN NS l.root-servers.net.
.. 43740 IN NS m.root-servers.net.
.. 43740 IN NS i.root-servers.net.
.. 43740 IN NS e.root-servers.net.
.. 43740 IN NS d.root-servers.net.
.. 43740 IN NS a.root-servers.net.
.. 43740 IN NS h.root-servers.net.
.. 43740 IN NS c.root-servers.net.
.. 43740 IN NS g.root-servers.net.
.. 43740 IN NS f.root-servers.net.
.. 43740 IN NS b.root-servers.net.
.. 43740 IN NS j.root-servers.net.
.. 43740 IN NS k.root-servers.net.
;; Received 449 bytes from 10.101.25.22#53(10.101.25.22) in 3 ms
com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
;; Received 500 bytes from 198.32.64.12#53(l.root-servers.net) in 94 ms
att.com. 172800 IN NS algw1.att.com.
att.com. 172800 IN NS kcgw1.att.com.
att.com. 172800 IN NS kcgw2.att.com.
;; Received 152 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 21 ms
www.businessdirect.att.com. 86400 IN CNAME cp.eia.att.com.
eia.att.com. 86400 IN NS alalia.att.com.
eia.att.com. 86400 IN NS kcalia.att.com.
;; Received 139 bytes from 192.128.133.77#53(kcgw1.att.com) in 55 ms
*******Here is a working and nonworking resolution from an XP box inside our
network:
C:\Documents and Settings\Administrator.GXCIT>nslookup www.yahoo.com
Server: bdc-wt.gxcit.com
Address: 10.101.60.11
Non-authoritative answer:
Name: www.yahoo.akadns.net
Addresses: 68.142.226.35, 68.142.226.53, 68.142.226.32, 68.142.226.51
68.142.226.50, 68.142.226.47, 68.142.226.38, 68.142.226.46
Aliases: www.yahoo.com
C:\Documents and Settings\Administrator.GXCIT>nslookup
www.businessdirect.att.com
Server: bdc-wt.gxcit.com
Address: 10.101.60.11
DNS request timed out.
timeout was 2 seconds.
*** Request to bdc-wt.gxcit.com timed-out
C:\Documents and Settings\Administrator.GXCIT>nslookup
www.businessdirect.att.com
Server: bdc-wt.gxcit.com
Address: 10.101.60.11
DNS request timed out.
timeout was 2 seconds.
*** Request to bdc-wt.gxcit.com timed-out
*******Here is some more troubleshooting:
#> nslookup
> server alalia.att.com
Default server: alalia.att.com
Address: 192.20.5.3#53
> eia.att.com
Server: alalia.att.com
Address: 192.20.5.3#53
Name: eia.att.com
Address: 192.20.5.11
> cp.eia.att.com
Server: alalia.att.com
Address: 192.20.5.3#53
Name: cp.eia.att.com
Address: 192.20.5.62
> server bdc-wt
Default server: bdc-wt
Address: 10.101.60.11#53
> cp.eia.att.com
Server: bdc-wt
Address: 10.101.60.11#53
** server can't find cp.eia.att.com: SERVFAIL
Am am lost as to what the next troubleshooting step will be! My searching of
the MSKB and the net have found very few problems similar to this. The few
that were found had no resolutions posted! Please help!
Thanks to any experts that take the time to get this far in reading this
message!
.
- Follow-Ups:
- Re: Can't Resolve Certain internet DNS names
- From: Kevin D. Goodknecht Sr. [MVP]
- Re: Can't Resolve Certain internet DNS names
- Prev by Date: RE: DNS error 0x0000232b when trying to join the domain.
- Next by Date: Re: Reverse PTR problems
- Previous by thread: Reverse PTR problems
- Next by thread: Re: Can't Resolve Certain internet DNS names
- Index(es):
Relevant Pages
|