Say your dns server did not answer you in a timely fashion. Set a timer to wait longer in dig, so does your AD query roots or forward?
C:\Users\user>dig en.community.dell.com +time=30
; <<>> DiG 9.9.5-W1 <<>> en.community.dell.com +time=30
;; global options: +cmd
;; connection timed out; no servers could be reached
Extended the time and still nothing.
About the AD, here is the DNS section:
A quick translation:
Visor de sucesos = Event log (there no errors from this year or last even)
Zonas de busqueda directa = Forward lookup Zones
Zonas de busqueda inserva = Reverse lookup Zones
Where should I look for this information you are asking me?
Why don't you try looking up something else? Seems odd to me that it takes your dns 150ms to return the root servers? But he answered atleast -- so your timeout lookup up the dell records just means he did not find it from who he asks and so why it timed out asking him.. Did you try it again in a second or so? See if he got an answer by then? If not you need to move up the chain to see why your having a problem?
Im gonna do a google.com
; <<>> DiG 9.9.5-W1 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58950
;; flags: qr aa; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 300 IN A 22.214.171.124
google.com. 300 IN A 126.96.36.199
google.com. 300 IN A 188.8.131.52
google.com. 300 IN A 184.108.40.206
google.com. 300 IN A 220.127.116.11
google.com. 300 IN A 18.104.22.168
google.com. 300 IN A 22.214.171.124
google.com. 300 IN A 126.96.36.199
google.com. 300 IN A 188.8.131.52
google.com. 300 IN A 184.108.40.206
google.com. 300 IN A 220.127.116.11
;; Query time: 110 msec
;; SERVER: 192.168.100.29#53(192.168.100.29)
;; WHEN: Thu Feb 20 15:50:47 Hora estßndar romance 2014
;; MSG SIZE rcvd: 215
so you can lookup who the authoritative dns is with a whois
user@linuxbox:~$ whois en.community.dell.com
Whois Server Version 2.0
Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.
No match for "EN.COMMUNITY.DELL.COM".
>>> Last update of whois database: Thu, 20 Feb 2014 14:59:11 UTC <<<
NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
reserves the right to modify these terms at any time.
The Registry database contains ONLY .COM, .NET, .EDU domains and
Domain Name: DELL.COM
Registrar: SAFENAMES LTD
Name Server: NS1.US.DELL.COM
Name Server: NS2.US.DELL.COM
Name Server: NS3.US.DELL.COM
Name Server: NS4.US.DELL.COM
Name Server: NS5.US.DELL.COM
So can you query one of those directly for that dell record?
I pinged the first one ns1.us.dell.com and didn't reply or even resolve a IP...
C:\>dig @ns1.us.dell.com en.community.dell.com
Couldn't find anything either...
If you can not query the authoritative servers for that domain, its possible you have network connectivity issue to that netblock if your asking roots. Or the dns servers your forwarding too have an issue, like I said you need to move up the chain of dns your using to find where the problem is. If you directly ask where you forward and he can not look it up, but you can from directly from authoritative servers.. Then your forwarder has a problem - you should report it to them. Or use a different one, or use multiple forwarders.
Well, tomorrow the people who we pay for internet access (not our ISP) comes to better a deal; They aren't in the technical area but I will talk to them about this issue and see what they say...