Accessibility Resource Center Skip to main content
Have a phone you love? Get up to $500 when you switch and bring your phone.

DNS issue in Northern NJ: SERVFAIL 71.250.0.12 and 68.237.161.12

Reply
DG12
Copper Contributor
Copper Contributor
Posts: 13
Registered: ‎03-29-2012

DNS issue in Northern NJ: SERVFAIL 71.250.0.12 and 68.237.161.12

Message 1 of 1
(995 Views)

at 12:50EDT

Router DNS Server:71.250.0.12 and 68.237.161.12

++++++++

 dig @71.250.0.12 autoinsurancecoverageverify.com

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 6032

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; Query time: 14 msec

;; SERVER: 71.250.0.12#53(71.250.0.12)

;; WHEN: Sun Dec  7 12:24:17 2014

;; MSG SIZE  rcvd: 49

++++++++

dig @68.237.161.12 autoinsurancecoverageverify.com

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 49699

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

 

;; Query time: 214 msec

;; SERVER: 68.237.161.12#53(68.237.161.12)

;; WHEN: Sun Dec  7 12:24:35 2014

+++++

 dig @68.237.161.12 autoinsurancecoverageverify.com +trace

. 403220 IN NS k.root-servers.net.

. 403220 IN NS j.root-servers.net.

. 403220 IN NS d.root-servers.net.

. 403220 IN NS b.root-servers.net.

. 403220 IN NS c.root-servers.net.

. 403220 IN NS e.root-servers.net.

. 403220 IN NS h.root-servers.net.

. 403220 IN NS a.root-servers.net.

. 403220 IN NS m.root-servers.net.

. 403220 IN NS i.root-servers.net.

. 403220 IN NS l.root-servers.net.

. 403220 IN NS g.root-servers.net.

. 403220 IN NS f.root-servers.net.

;; Received 508 bytes from 68.237.161.12#53(68.237.161.12) in 243 ms

 

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.

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.

;; Received 509 bytes from 128.63.2.53#53(128.63.2.53) in 25 ms

 

autoinsurancecoverageverify.com. 172800 IN NS ns41.domaincontrol.com.

autoinsurancecoverageverify.com. 172800 IN NS ns42.domaincontrol.com.

;; Received 133 bytes from 192.31.80.30#53(192.31.80.30) in 25 ms

 

autoinsurancecoverageverify.com. 3600 IN A 50.63.41.190

autoinsurancecoverageverify.com. 3600 IN NS ns42.domaincontrol.com.

autoinsurancecoverageverify.com. 3600 IN NS ns41.domaincontrol.com.

;; Received 117 bytes from 216.69.185.21#53(216.69.185.21) in 23 ms

 

/Users/dgerman/internet > dig autoinsurancecoverageverify.com +trace

. 3600 IN NS FWDR-71.FWDR-250.FWDR-0.FWDR-12.

. 3600 IN NS FWDR-68.FWDR-237.FWDR-161.FWDR-12.

;; Received 196 bytes from 192.168.1.1#53(192.168.1.1) in 71 ms

 

autoinsurancecoverageverify.com. 169483 IN NS ns42.domaincontrol.com.

autoinsurancecoverageverify.com. 169483 IN NS ns41.domaincontrol.com.

;; Received 133 bytes from 68.237.161.12#53(68.237.161.12) in 13 ms

 

autoinsurancecoverageverify.com. 3600 IN A 50.63.41.190

autoinsurancecoverageverify.com. 3600 IN NS ns42.domaincontrol.com.

autoinsurancecoverageverify.com. 3600 IN NS ns41.domaincontrol.com.

;; Received 117 bytes from 216.69.185.21#53(216.69.185.21) in 23 ms

 

 +++++++++  Whoa!  ++++

dig @68.237.161.12 autoinsurancecoverageverify.com       

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54597

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

 

;; ANSWER SECTION:

autoinsurancecoverageverify.com. 1855 IN A 50.63.41.190

 

;; Query time: 17 msec

;; SERVER: 68.237.161.12#53(68.237.161.12)

;; WHEN: Sun Dec  7 12:56:37 2014

++++++++++now SERVFAIL again!  +++++++

dig @68.237.161.12 autoinsurancecoverageverify.com  

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 5688

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

 

;; Query time: 13 msec

;; SERVER: 68.237.161.12#53(68.237.161.12)

;; WHEN: Sun Dec  7 12:58:23 2014

;; MSG SIZE  rcvd: 49

++++++++++

 

and now back at 71.250.0.12

+++++ SERVFAIL 

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 15697

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

 

;; Query time: 11 msec

;; SERVER: 71.250.0.12#53(71.250.0.12)

;; WHEN: Sun Dec  7 13:06:36 2014

+++++   WHOA !  success , but wait...

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30496

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

 

;; ANSWER SECTION:

autoinsurancecoverageverify.com. 3600 IN A  50.63.41.190

 

;; Query time: 22 msec

;; SERVER: 71.250.0.12#53(71.250.0.12)

;; WHEN: Sun Dec  7 13:06:38 2014

;; MSG SIZE  rcvd: 65

++++++   now a SERVFAIL again !!!

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 21546

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

 

;; Query time: 13 msec

;; SERVER: 71.250.0.12#53(71.250.0.12)

;; WHEN: Sun Dec  7 13:06:43 2014

;; MSG SIZE  rcvd: 49

 

 

 

HOW DO I REPORT THIS TO VERIZON ?????

 

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.
Have a spare Fios-G1100?Learn how to bridge it into your network
Get Started


Covid19

Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.
Modal Dialogue Title