Solved

DNS problems

Posted on 2003-12-10
48
751 Views
Last Modified: 2010-03-19
This morning I changed the nameserver settings for my domain name. The WHOIS result at http://195.66.240.211/cgi-bin/whois.cgi?query=puseyuk.co.uk shows that the update is successful, but the domain name still resolves to the old 81.3.70.130 address instead of the new 207.142.135.91 address. It's been 4 hours 20 mins since the nameserver update was made and it's never took this long for the address to change the last time I did it.

The problem is I need the fixed ASAP cos with the old address in use my site is down and my incomming emails are being lost! PLEASE HELP!
0
Comment
Question by:davepusey
  • 26
  • 15
  • 7
48 Comments
 
LVL 31

Expert Comment

by:qwaletee
ID: 9912711
Just to be sure, check teh zone records (DNS mappings) on your old primary name server, your old backup name server, your new primary name server, and your new backup name server
0
 
LVL 31

Expert Comment

by:qwaletee
ID: 9912726
And, you ave to check those settings for both A records and MX records.
0
 
LVL 31

Expert Comment

by:qwaletee
ID: 9912762
E:\Lotus\Domino>nslookup - ns3.eukdns.com
Default Server:  ns3.eukhost.com
Address:  64.5.60.201

> pusey.co.uk
Server:  ns3.eukhost.com
Address:  64.5.60.201

Name:    pusey.co.uk

> set type=mx
> pusey.co.uk
Server:  ns3.eukhost.com
Address:  64.5.60.201

Non-authoritative answer:
pusey.co.uk     MX preference = 99, mail exchanger = relay-1.mailbox.net.uk
pusey.co.uk     MX preference = 10, mail exchanger = mail.any-mail.co.uk

pusey.co.uk     nameserver = dns.mailbox.co.uk
pusey.co.uk     nameserver = ns1.mailbox.co.uk
dns.mailbox.co.uk       internet address = 195.82.96.40
>

the fact that your primary nameserver is returning a non-authoritative answer for your MX record would definitely bother me.

Also, note that neother of the two IP addresses you mention is present, and the MX record is pointing to a couple of other relay servers, and I don't know if those servers are set to relay mail properyly to you.

You seem to have a really hosed setup on your primary nameserver!!!!!!!!!!!!!!
0
 
LVL 31

Expert Comment

by:qwaletee
ID: 9912787
Using a third[arty nameserver (my primary), I get back another 195.82.*.* address for www, and for your MX, consistent with above:

pusey.co.uk     MX preference = 10, mail exchanger = mail.any-mail.co.uk
pusey.co.uk     MX preference = 99, mail exchanger = relay-1.mailbox.net.uk
pusey.co.uk     nameserver = dns.mailbox.co.uk
pusey.co.uk     nameserver = ns1.mailbox.co.uk
mail.any-mail.co.uk     internet address = 195.82.107.65
relay-1.mailbox.net.uk  internet address = 195.82.125.30
dns.mailbox.co.uk       internet address = 195.82.96.40
ns1.mailbox.co.uk       internet address = 195.82.96.6
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9912845
If that's really your domain, your delegation is hosed:
the co.uk authrority is referring to:
puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.

which doesn't have your zone records and is looping back:

C:\dig>dig +trace    puseyuk.co.uk

; <<>> DiG 9.2.2 <<>> +trace puseyuk.co.uk
;; global options:  printcmd
.                       267074  IN      NS      m.root-servers.net.
.                       267074  IN      NS      a.root-servers.net.
.                       267074  IN      NS      b.root-servers.net.
.                       267074  IN      NS      c.root-servers.net.
.                       267074  IN      NS      d.root-servers.net.
.                       267074  IN      NS      e.root-servers.net.
.                       267074  IN      NS      f.root-servers.net.
.                       267074  IN      NS      g.root-servers.net.
.                       267074  IN      NS      h.root-servers.net.
.                       267074  IN      NS      i.root-servers.net.
.                       267074  IN      NS      j.root-servers.net.
.                       267074  IN      NS      k.root-servers.net.
.                       267074  IN      NS      l.root-servers.net.
;; Received 436 bytes from 192.168.2.1#53(192.168.2.1) in 110 ms

uk.                     172800  IN      NS      NS1.NIC.uk.
uk.                     172800  IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     172800  IN      NS      NS2.NIC.uk.
uk.                     172800  IN      NS      NS4.NIC.uk.
uk.                     172800  IN      NS      NS3.NIC.uk.
uk.                     172800  IN      NS      NS5.NIC.uk.
;; Received 257 bytes from 202.12.27.33#53(m.root-servers.net) in 360 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 195.66.240.130#53(NS1.NIC.uk) in 150 ms

uk.                     17629   IN      NS      NS4.NIC.uk.
uk.                     17629   IN      NS      NS5.NIC.uk.
uk.                     17629   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17629   IN      NS      NS1.NIC.uk.
uk.                     17629   IN      NS      NS2.NIC.uk.
uk.                     17629   IN      NS      NS3.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 320 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 194.83.244.131#53(NS4.NIC.uk) in 290 ms

uk.                     17628   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17628   IN      NS      NS1.NIC.uk.
uk.                     17628   IN      NS      NS2.NIC.uk.
uk.                     17628   IN      NS      NS3.NIC.uk.
uk.                     17628   IN      NS      NS4.NIC.uk.
uk.                     17628   IN      NS      NS5.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 180 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 154.32.105.90#53(SEC-NOM.DNS.UK.PSI.NET) in 170 ms

uk.                     17627   IN      NS      NS5.NIC.uk.
uk.                     17627   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17627   IN      NS      NS1.NIC.uk.
uk.                     17627   IN      NS      NS2.NIC.uk.
uk.                     17627   IN      NS      NS3.NIC.uk.
uk.                     17627   IN      NS      NS4.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 270 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.246.167.131#53(NS5.NIC.uk) in 240 ms

uk.                     17627   IN      NS      NS5.NIC.uk.
uk.                     17627   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17627   IN      NS      NS1.NIC.uk.
uk.                     17627   IN      NS      NS2.NIC.uk.
uk.                     17627   IN      NS      NS3.NIC.uk.
uk.                     17627   IN      NS      NS4.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 280 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.246.167.131#53(NS5.NIC.uk) in 180 ms

uk.                     17626   IN      NS      NS5.NIC.uk.
uk.                     17626   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17626   IN      NS      NS1.NIC.uk.
uk.                     17626   IN      NS      NS2.NIC.uk.
uk.                     17626   IN      NS      NS3.NIC.uk.
uk.                     17626   IN      NS      NS4.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 410 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.246.167.131#53(NS5.NIC.uk) in 180 ms

uk.                     17625   IN      NS      NS1.NIC.uk.
uk.                     17625   IN      NS      NS2.NIC.uk.
uk.                     17625   IN      NS      NS3.NIC.uk.
uk.                     17625   IN      NS      NS4.NIC.uk.
uk.                     17625   IN      NS      NS5.NIC.uk.
uk.                     17625   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 280 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 195.66.240.130#53(NS1.NIC.uk) in 280 ms

uk.                     17624   IN      NS      NS4.NIC.uk.
uk.                     17624   IN      NS      NS5.NIC.uk.
uk.                     17624   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17624   IN      NS      NS1.NIC.uk.
uk.                     17624   IN      NS      NS2.NIC.uk.
uk.                     17624   IN      NS      NS3.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 270 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 194.83.244.131#53(NS4.NIC.uk) in 290 ms

uk.                     17624   IN      NS      NS1.NIC.uk.
uk.                     17624   IN      NS      NS2.NIC.uk.
uk.                     17624   IN      NS      NS3.NIC.uk.
uk.                     17624   IN      NS      NS4.NIC.uk.
uk.                     17624   IN      NS      NS5.NIC.uk.
uk.                     17624   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 290 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 195.66.240.130#53(NS1.NIC.uk) in 220 ms

uk.                     17623   IN      NS      NS1.NIC.uk.
uk.                     17623   IN      NS      NS2.NIC.uk.
uk.                     17623   IN      NS      NS3.NIC.uk.
uk.                     17623   IN      NS      NS4.NIC.uk.
uk.                     17623   IN      NS      NS5.NIC.uk.
uk.                     17623   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 320 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 195.66.240.130#53(NS1.NIC.uk) in 220 ms

uk.                     17622   IN      NS      NS5.NIC.uk.
uk.                     17622   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17622   IN      NS      NS1.NIC.uk.
uk.                     17622   IN      NS      NS2.NIC.uk.
uk.                     17622   IN      NS      NS3.NIC.uk.
uk.                     17622   IN      NS      NS4.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 470 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.246.167.131#53(NS5.NIC.uk) in 240 ms

uk.                     17621   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17621   IN      NS      NS1.NIC.uk.
uk.                     17621   IN      NS      NS2.NIC.uk.
uk.                     17621   IN      NS      NS3.NIC.uk.
uk.                     17621   IN      NS      NS4.NIC.uk.
uk.                     17621   IN      NS      NS5.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 260 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 154.32.105.90#53(SEC-NOM.DNS.UK.PSI.NET) in 300 ms

uk.                     17621   IN      NS      NS1.NIC.uk.
uk.                     17621   IN      NS      NS2.NIC.uk.
uk.                     17621   IN      NS      NS3.NIC.uk.
uk.                     17621   IN      NS      NS4.NIC.uk.
uk.                     17621   IN      NS      NS5.NIC.uk.
uk.                     17621   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 300 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 195.66.240.130#53(NS1.NIC.uk) in 220 ms

uk.                     17620   IN      NS      NS5.NIC.uk.
uk.                     17620   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17620   IN      NS      NS1.NIC.uk.
uk.                     17620   IN      NS      NS2.NIC.uk.
uk.                     17620   IN      NS      NS3.NIC.uk.
uk.                     17620   IN      NS      NS4.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 300 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.246.167.131#53(NS5.NIC.uk) in 180 ms

uk.                     17619   IN      NS      NS3.NIC.uk.
uk.                     17619   IN      NS      NS4.NIC.uk.
uk.                     17619   IN      NS      NS5.NIC.uk.
uk.                     17619   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17619   IN      NS      NS1.NIC.uk.
uk.                     17619   IN      NS      NS2.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 300 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.219.13.131#53(NS3.NIC.uk) in 200 ms

uk.                     17618   IN      NS      NS4.NIC.uk.
uk.                     17618   IN      NS      NS5.NIC.uk.
uk.                     17618   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17618   IN      NS      NS1.NIC.uk.
uk.                     17618   IN      NS      NS2.NIC.uk.
uk.                     17618   IN      NS      NS3.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 300 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
dig: Too many lookups
0
 
LVL 2

Author Comment

by:davepusey
ID: 9913231
This is what my welcome email from the hosting company said regarding nameservers...

-------------------------------------------------------------------------------------------------------
Transferring Your Domain To Us
As you have selected you already have your domain you will need to transfer this to us.

Please change your nameservers to the following:

  Nameserver 1: ns3.eukdns.com

  Nameserver 2: ns4.eukdns.com
-------------------------------------------------------------------------------------------------------

Also, chicagoan's results are consistant with mine.

qwaletee, what happens if you put http://www.puseyuk.co.uk into your web browser?
0
 
LVL 2

Author Comment

by:davepusey
ID: 9913251
In fact qwaletee you've got my domain name wrong it is PUSEYUK.CO.UK
0
 
LVL 2

Author Comment

by:davepusey
ID: 9913286
When i do nslookup i get this...

2      puseyuk.co.uk      ALL      Query sent to      ns3.eukdns.com
2      puseyuk.co.uk      MX      14400      puseyuk.co.uk      0
2      puseyuk.co.uk      SOA      14400      ns3.eukdns.com      root.spirit.eukhost.com      2003120902      28800      7200      3600000      86400
2      puseyuk.co.uk      NS      14400      ns4.eukdns.com      
2      puseyuk.co.uk      NS      14400      ns3.eukdns.com      
2      puseyuk.co.uk      A      14400      207.142.135.91      
2      puseyuk.co.uk      A      14400      207.142.135.91      
2      ns3.eukdns.com      A      14400      64.5.60.201      
2      ns4.eukdns.com      A      14400      64.5.60.219      
2      Lookup complete

The IP addresses of the A tag match that of the webserver serving the domain.
0
 
LVL 2

Author Comment

by:davepusey
ID: 9913329
And if i do nslookup using my ISP dns i get this...

3      puseyuk.co.uk      ALL      Query sent to      192.168.0.1
3      puseyuk.co.uk      SOA      9463      ns.sovdns3.com      admin.ns.sovdns3.com      1067945475      10800      3600      604800      86400
3      puseyuk.co.uk      NS      89700      ns.sovdns3.com      
3      puseyuk.co.uk      NS      89700      ns.compila4.net      
3      ns.sovdns3.com      A      102505      81.3.70.130      
3      ns.compila4.net      A      79563      217.199.165.77      
3      Lookup complete
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9913337
eukdns.com has your zone file, but there's no way to know that unless the .uk name servers do, and THEY have your zone delegated to
puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.


0
 
LVL 2

Author Comment

by:davepusey
ID: 9913369
The ISP dns is showing the old nameserver info. Its been 6 hours since the change. Surely thats plenty of time to the update to occur?
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9913413
You have to get your delegation straightened out.

the .uk nameservers have to refer to

ns3.eukdns.com                    64.5.60.201
ns4.eukdns.com                    64.5.60.219

NOT

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.

and Fasthosts has to do it.

BTW: I'm not fond of registrars who obfuscate registrant info. They are a spammer's delight.
0
 
LVL 2

Author Comment

by:davepusey
ID: 9913454
The nameservers ARE pointing to

ns3.eukdns.com                    64.5.60.201
ns4.eukdns.com                    64.5.60.219

the only reason your getting

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.

is cos you ISP's DNS hasnt updated yet.

Is it possible to do somthing like this... http://www.busan.edu/~nic/networking/dnsbind/ch10_02.htm and cause the update to occur now and not when the 3 hour refresh has expired (which it has twice now already and still no update - strange!)
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9913526
Dave,
 Send the dig trace above to Fasthost tech support.

0
 
LVL 2

Author Comment

by:davepusey
ID: 9913641
Whats a dig trace?
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9913673
dig +trace    puseyuk.co.uk

; <<>> DiG 9.2.2 <<>> +trace puseyuk.co.uk
;; global options:  printcmd
.                       267074  IN      NS      m.root-servers.net.
.                       267074  IN      NS      a.root-servers.net.
.                       267074  IN      NS      b.root-servers.net.
.                       267074  IN      NS      c.root-servers.net.
.                       267074  IN      NS      d.root-servers.net.
.                       267074  IN      NS      e.root-servers.net.
.                       267074  IN      NS      f.root-servers.net.
.                       267074  IN      NS      g.root-servers.net.
.                       267074  IN      NS      h.root-servers.net.
.                       267074  IN      NS      i.root-servers.net.
.                       267074  IN      NS      j.root-servers.net.
.                       267074  IN      NS      k.root-servers.net.
.                       267074  IN      NS      l.root-servers.net.
;; Received 436 bytes from 192.168.2.1#53(192.168.2.1) in 110 ms

uk.                     172800  IN      NS      NS1.NIC.uk.
uk.                     172800  IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     172800  IN      NS      NS2.NIC.uk.
uk.                     172800  IN      NS      NS4.NIC.uk.
uk.                     172800  IN      NS      NS3.NIC.uk.
uk.                     172800  IN      NS      NS5.NIC.uk.
;; Received 257 bytes from 202.12.27.33#53(m.root-servers.net) in 360 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 195.66.240.130#53(NS1.NIC.uk) in 150 ms

uk.                     17629   IN      NS      NS4.NIC.uk.
uk.                     17629   IN      NS      NS5.NIC.uk.
uk.                     17629   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17629   IN      NS      NS1.NIC.uk.
uk.                     17629   IN      NS      NS2.NIC.uk.
uk.                     17629   IN      NS      NS3.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 320 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 194.83.244.131#53(NS4.NIC.uk) in 290 ms

uk.                     17628   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17628   IN      NS      NS1.NIC.uk.
uk.                     17628   IN      NS      NS2.NIC.uk.
uk.                     17628   IN      NS      NS3.NIC.uk.
uk.                     17628   IN      NS      NS4.NIC.uk.
uk.                     17628   IN      NS      NS5.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 180 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 154.32.105.90#53(SEC-NOM.DNS.UK.PSI.NET) in 170 ms

uk.                     17627   IN      NS      NS5.NIC.uk.
uk.                     17627   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17627   IN      NS      NS1.NIC.uk.
uk.                     17627   IN      NS      NS2.NIC.uk.
uk.                     17627   IN      NS      NS3.NIC.uk.
uk.                     17627   IN      NS      NS4.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 270 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.246.167.131#53(NS5.NIC.uk) in 240 ms

uk.                     17627   IN      NS      NS5.NIC.uk.
uk.                     17627   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17627   IN      NS      NS1.NIC.uk.
uk.                     17627   IN      NS      NS2.NIC.uk.
uk.                     17627   IN      NS      NS3.NIC.uk.
uk.                     17627   IN      NS      NS4.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 280 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.246.167.131#53(NS5.NIC.uk) in 180 ms

uk.                     17626   IN      NS      NS5.NIC.uk.
uk.                     17626   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17626   IN      NS      NS1.NIC.uk.
uk.                     17626   IN      NS      NS2.NIC.uk.
uk.                     17626   IN      NS      NS3.NIC.uk.
uk.                     17626   IN      NS      NS4.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 410 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.246.167.131#53(NS5.NIC.uk) in 180 ms

uk.                     17625   IN      NS      NS1.NIC.uk.
uk.                     17625   IN      NS      NS2.NIC.uk.
uk.                     17625   IN      NS      NS3.NIC.uk.
uk.                     17625   IN      NS      NS4.NIC.uk.
uk.                     17625   IN      NS      NS5.NIC.uk.
uk.                     17625   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 280 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 195.66.240.130#53(NS1.NIC.uk) in 280 ms

uk.                     17624   IN      NS      NS4.NIC.uk.
uk.                     17624   IN      NS      NS5.NIC.uk.
uk.                     17624   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17624   IN      NS      NS1.NIC.uk.
uk.                     17624   IN      NS      NS2.NIC.uk.
uk.                     17624   IN      NS      NS3.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 270 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 194.83.244.131#53(NS4.NIC.uk) in 290 ms

uk.                     17624   IN      NS      NS1.NIC.uk.
uk.                     17624   IN      NS      NS2.NIC.uk.
uk.                     17624   IN      NS      NS3.NIC.uk.
uk.                     17624   IN      NS      NS4.NIC.uk.
uk.                     17624   IN      NS      NS5.NIC.uk.
uk.                     17624   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 290 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 195.66.240.130#53(NS1.NIC.uk) in 220 ms

uk.                     17623   IN      NS      NS1.NIC.uk.
uk.                     17623   IN      NS      NS2.NIC.uk.
uk.                     17623   IN      NS      NS3.NIC.uk.
uk.                     17623   IN      NS      NS4.NIC.uk.
uk.                     17623   IN      NS      NS5.NIC.uk.
uk.                     17623   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 320 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 195.66.240.130#53(NS1.NIC.uk) in 220 ms

uk.                     17622   IN      NS      NS5.NIC.uk.
uk.                     17622   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17622   IN      NS      NS1.NIC.uk.
uk.                     17622   IN      NS      NS2.NIC.uk.
uk.                     17622   IN      NS      NS3.NIC.uk.
uk.                     17622   IN      NS      NS4.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 470 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.246.167.131#53(NS5.NIC.uk) in 240 ms

uk.                     17621   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17621   IN      NS      NS1.NIC.uk.
uk.                     17621   IN      NS      NS2.NIC.uk.
uk.                     17621   IN      NS      NS3.NIC.uk.
uk.                     17621   IN      NS      NS4.NIC.uk.
uk.                     17621   IN      NS      NS5.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 260 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 154.32.105.90#53(SEC-NOM.DNS.UK.PSI.NET) in 300 ms

uk.                     17621   IN      NS      NS1.NIC.uk.
uk.                     17621   IN      NS      NS2.NIC.uk.
uk.                     17621   IN      NS      NS3.NIC.uk.
uk.                     17621   IN      NS      NS4.NIC.uk.
uk.                     17621   IN      NS      NS5.NIC.uk.
uk.                     17621   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 300 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 195.66.240.130#53(NS1.NIC.uk) in 220 ms

uk.                     17620   IN      NS      NS5.NIC.uk.
uk.                     17620   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17620   IN      NS      NS1.NIC.uk.
uk.                     17620   IN      NS      NS2.NIC.uk.
uk.                     17620   IN      NS      NS3.NIC.uk.
uk.                     17620   IN      NS      NS4.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 300 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.246.167.131#53(NS5.NIC.uk) in 180 ms

uk.                     17619   IN      NS      NS3.NIC.uk.
uk.                     17619   IN      NS      NS4.NIC.uk.
uk.                     17619   IN      NS      NS5.NIC.uk.
uk.                     17619   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17619   IN      NS      NS1.NIC.uk.
uk.                     17619   IN      NS      NS2.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 300 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
;; Received 88 bytes from 213.219.13.131#53(NS3.NIC.uk) in 200 ms

uk.                     17618   IN      NS      NS4.NIC.uk.
uk.                     17618   IN      NS      NS5.NIC.uk.
uk.                     17618   IN      NS      SEC-NOM.DNS.UK.PSI.NET.
uk.                     17618   IN      NS      NS1.NIC.uk.
uk.                     17618   IN      NS      NS2.NIC.uk.
uk.                     17618   IN      NS      NS3.NIC.uk.
;; Received 161 bytes from 81.3.70.130#53(ns.sovdns3.com) in 300 ms

puseyuk.co.uk.          172800  IN      NS      ns.sovdns3.com.
puseyuk.co.uk.          172800  IN      NS      ns.compila4.net.
dig: Too many lookups

0
 
LVL 2

Author Comment

by:davepusey
ID: 9913756
Oh, that thingy!
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9913877
<!>
0
 
LVL 2

Author Comment

by:davepusey
ID: 9914029
It's now 7 hours since the nameservers were changed. I sent that thingy to them and they said it usally take about 10 hours to update.
0
 
LVL 2

Author Comment

by:davepusey
ID: 9915099
9 hours 22 mins and still no update.
0
 
LVL 2

Author Comment

by:davepusey
ID: 9915329
Now at 9 hours 53 mins
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9916735
Nothing's been fixed:
Maybe I didn't explain it clearly enough:

Here I am asking NS1.NIC.UK for your A record. This is one of the root servers for the .uk domain:
 
; <<>> DiG 2.1 <<>> @NS1.NIC.uk. puseyuk.co.uk A  
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr rd; Ques: 1, Ans: 0, Auth: 2, Addit: 0
;; QUESTIONS:
;; puseyuk.co.uk, type = A, class = IN

And here it is telling me, as I expect it to, that it doesn't have a record but it knows who is authoritative for your domain:
 
;; AUTHORITY RECORDS:
puseyuk.co.uk. 172800 NS ns.sovdns3.com.  
puseyuk.co.uk. 172800 NS ns.compila4.net.  

;; Total query time: 157 msec
;; FROM: us.mirror.menandmice.com to SERVER: NS1.NIC.uk. 195.66.240.130
;; WHEN: Wed Dec 10 15:56:15 2003
;; MSG SIZE sent: 31 rcvd: 88

BUT! that's not right, fasthost says it should be:
ns3.eukdns.com                    64.5.60.201
ns4.eukdns.com                    64.5.60.219

and once againTHAT is the problem

The whois database is NOT DNS. It says what should be in DNS.
and what it says is NOT in DNS
and that's why your DNS isn't working!

So you have to get to your registrar (fasthost) and tell them to get off their lazy duffs, read the dig trace, and fix your delegation on the bloody UK root servers!

0
 
LVL 2

Author Comment

by:davepusey
ID: 9919030
Well I do i dig at NS1.NIC.uk and get this...

12/11/03 09:26:58 dig puseyuk.co.uk @ NS1.NIC.uk
Dig puseyuk.co.uk@NS1.NIC.uk (195.66.240.130) ...
Non-authoritative answer
 Query for puseyuk.co.uk type=255 class=1
  puseyuk.co.uk NS (Nameserver) ns3.eukdns.com
  puseyuk.co.uk NS (Nameserver) ns4.eukdns.com
  puseyuk.co.uk NS (Nameserver) ns3.eukdns.com
  puseyuk.co.uk NS (Nameserver) ns4.eukdns.com
0
 
LVL 2

Author Comment

by:davepusey
ID: 9919034
Now at 23 hours 49 mins
0
Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

 
LVL 2

Author Comment

by:davepusey
ID: 9919039
So as far as I can see, I'm just waiting for the ISP DNS servers to update.
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9919137
So they changed it sometime after Wed Dec 10 15:56:15 2003

and it's gotten here:

; <<>> DiG 2.1 <<>> @ NS02.JDC01.PA.COMCAST.NET puseyuk.co.uk A  
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr aa rd ra; Ques: 1, Ans: 1, Auth: 2, Addit: 2
;; QUESTIONS:
;; puseyuk.co.uk, type = A, class = IN
 
;; ANSWERS:
puseyuk.co.uk. 14400 A 207.142.135.91  
 
;; AUTHORITY RECORDS:
puseyuk.co.uk. 172785 NS ns4.eukdns.com.  
puseyuk.co.uk. 172785 NS ns3.eukdns.com.  
 
;; ADDITIONAL RECORDS:
ns4.eukdns.com. 172785 A 64.5.60.219  
ns3.eukdns.com. 172785 A 64.5.60.201  
 
;; Total query time: 41 msec
;; FROM: us.mirror.menandmice.com to SERVER: default -- 0.0.0.0
;; WHEN: Thu Dec 11 02:57:15 2003
;; MSG SIZE sent: 31 rcvd: 138


looks like they fixed it
0
 
LVL 2

Author Comment

by:davepusey
ID: 9919232
What happens if you go to www.puseyuk.co.uk ? At moment I get "The page cannot be displayed - Cannot find server/DNS error". What do u get?
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9919875
depending on what resolver i use i get your apache default page or a lookup failure
your seeing the results of negative caching on your local name server.
you zone's ttl is set to 1 day (see below)
since the old nameservers were authoritative when you last queried and couldn't resolve, they hold onto that info
the domain existed but there was no A record, so now you're waiting for your DNS server's cache to flush
try your query at a few other DNS servers



;; global options:  printcmd
puseyuk.co.uk.          14400   IN      SOA     ns3.eukdns.com. root.spirit.eukh
ost.com. 2003120902 28800 7200 3600000 86400
puseyuk.co.uk.          14400   IN      MX      0 puseyuk.co.uk.
puseyuk.co.uk.          14400   IN      NS      ns3.eukdns.com.
puseyuk.co.uk.          14400   IN      NS      ns4.eukdns.com.
puseyuk.co.uk.          14400   IN      A       207.142.135.91
ftp.puseyuk.co.uk.      14400   IN      A       207.142.135.91
localhost.puseyuk.co.uk. 14400  IN      A       127.0.0.1
mail.puseyuk.co.uk.     14400   IN      CNAME   puseyuk.co.uk.
temp.puseyuk.co.uk.     14400   IN      A       207.142.135.91
www.temp.puseyuk.co.uk. 14400   IN      A       207.142.135.91
www.puseyuk.co.uk.      14400   IN      CNAME   puseyuk.co.uk.
puseyuk.co.uk.          14400   IN      SOA     ns3.eukdns.com. root.spirit.eukh
ost.com. 2003120902 28800 7200 3600000 86400
;; Query time: 490 msec
;; SERVER: 64.5.60.201#53(ns3.eukdns.com)
;; WHEN: Thu Dec 11 07:35:35 2003
0
 
LVL 2

Author Comment

by:davepusey
ID: 9919930
>> i get your apache default page

Do u mean the homepage of my site (index.php) or that page you get just after you've installed apache (the one that says "If you can see this, it means that the installation of the Apache web server software on this system was successful. You may now add content to this directory and replace this page.")?
0
 
LVL 2

Author Comment

by:davepusey
ID: 9919952
If I put the following in my HOSTS file I get the welcome page of my website. This is what you should get too even when using DNS to resolve instead of HOSTS.

207.142.135.91      www.puseyuk.co.uk
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9919953
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
 <HEAD>
  <TITLE>Test Page for the SSL/TLS-aware Apache Installation on Web Site</TITLE>
  <STYLE TYPE="text/css">
  H1 {
      font-weight: bold;
      font-size: 18pt;
      line-height: 18pt;
      font-family: arial,helvetica;
      font-variant: normal;
      font-style: normal;
  }
  BODY {
      color: black;
      background-color: white;
      background-image: url(manual/images/feather.jpg);
      background-repeat: no-repeat;
  }
  </STYLE>
 </HEAD>
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
 <BODY
  BGCOLOR="#FFFFFF"
  TEXT="#000000"
  LINK="#0000FF"
  VLINK="#0000FF"
  ALINK="#FF0000"
 >
  <BLOCKQUOTE>
  <BLOCKQUOTE>
  <BR>
  <H1>
  Hey, it worked <I>!</I><BR>
  The SSL/TLS-aware Apache webserver was<BR>
  successfully installed on this website.
  </H1>
  <P>
  If you can see this page, then the people who own this website have just
  installed the <A HREF="http://www.apache.org/">Apache Web server</A>
  software and the <A HREF="http://www.modssl.org/">Apache
  Interface to OpenSSL (mod_ssl)</A> successfully.  They now have to add
  content to this directory and replace this placeholder page, or else point
  the server at their real content.
  </P>
  <BLOCKQUOTE>
   <STRONG>ATTENTION!</STRONG><BR>
   If you are seeing this page instead of the site you expected, please
   <STRONG>contact the administrator of the site involved.</STRONG>
   (Try sending mail to <SAMP>&lt;webmaster@<EM>domain</EM>&gt;</SAMP>.)
   Although this site is
   running the Apache software it almost certainly has no other connection
   to the Apache Group, so please do not send mail about this site or its
   contents to the Apache authors.  If you do, your message will be
   <STRONG>ignored</STRONG>.
  </BLOCKQUOTE>
  <P>
  The Apache online
  <A
   HREF="manual/index.html"
  >documentation</A>
  has been included with this distribution.<BR>
  Especially also read the
  <A
   HREF="manual/mod/mod_ssl/"
  >mod_ssl User Manual</A>
  carefully.
  </P>
  <P>
  Your are allowed to use the images below on your SSL-aware Apache Web server.<BR>
  Thanks for using Apache, mod_ssl and OpenSSL!
  </P>
  <P>
  <DIV ALIGN="CENTER">
   <A HREF="http://www.apache.org/"
   ><IMG SRC="manual/images/apache_pb.gif" ALT="Apache Webserver" BORDER=0></A>
   &nbsp;
   <A HREF="http://www.modssl.org/"
   ><IMG SRC="manual/images/mod_ssl_sb.gif" ALT="mod_ssl Interface" BORDER=0></A>
   &nbsp;
   <A HREF="http://www.openssl.org/"
   ><IMG SRC="manual/images/openssl_ics.gif" ALT="OpenSSL Toolkit" BORDER=0></A>
  </DIV>
  </BLOCKQUOTE>
  </BLOCKQUOTE>
 </BODY>
</HTML>
0
 
LVL 2

Author Comment

by:davepusey
ID: 9920000
Well I get the welcome page of my website. Why do you think you could be getting that?

Also, you say the zone ttl is 1 day, what does that mean?

It's now 27h02m since the nameserver change.
0
 
LVL 2

Author Comment

by:davepusey
ID: 9920078
Well something must be wrong only for you cos, according to transfer logs, Googlebot and some visitors have managed to browse round the new server without any probs.
0
 
LVL 2

Author Comment

by:davepusey
ID: 9920109
Even samspade returns the correct page... http://www.samspade.org/t/safe?u=http%3A%2F%2Fwww.puseyuk.co.uk
0
 
LVL 18

Accepted Solution

by:
chicagoan earned 500 total points
ID: 9920276
I accessed the page by it's IP
You're processing the url get someplace other than the default page of the root.
It may be 27 hours since the whois database was changed, but the delegation wasn't figed until sometime after Wed Dec 10 15:56:15 2003 (zulu)
You have to start your coundtdown from the time the DNS records were fixed.
ttl means Time To Live. When a nameserver resolves an address, it will cache the result for the amount of time specified in the zone file, in this case 24 hours.
0
 
LVL 2

Author Comment

by:davepusey
ID: 9920382
>> You're processing the url get someplace other than the default page of the root.

Erh! Care to elaborate?
0
 
LVL 2

Author Comment

by:davepusey
ID: 9920427
>> zulu

I've heard that before in Stargate SG1. Does that mean GMT/UTC?
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9920467
The world is divided into 24 time zones. For easy reference in communications, a letter of the alphabet has been assigned to each time zone (less the letters "I" and "O"). The "clock" at Greenwich, England is used as the standard clock for international reference of time in communications, military, maritime and other activities that cross time zones. The letter designator for this clock is Z.
Times are usually written in military time or 24 hour format such as 1830Z. To pronounce this, the phonetic alphabet is used for the letter Z, or Zulu. This time is sometimes referred to as Zulu Time because of its assigned letter. It's official name is Coordinated Universal Time or UTC. Previously it had been known as Greenwich Mean Time or GMT but this has been replaced with UTC.
I'm not sure where the Stargate Portal is located, so I can't address their use of the term.
0
 
LVL 2

Author Comment

by:davepusey
ID: 9920484
>> zulu
>>
>> I've heard that before in Stargate SG1. Does that mean GMT/UTC?

Of cause it is! Silly me!

>> It may be 27 hours since the whois database was changed, but the delegation wasn't figed until sometime after Wed
>> Dec 10 15:56:15 2003 (zulu)

Even then, the elapsed time is 22h56m
0
 
LVL 2

Author Comment

by:davepusey
ID: 9920520
>> I'm not sure where the Stargate Portal is located, so I can't address their use of the term.

It's in cheyenne mountain (under NORAD). In one episode, they used the zulu timezone as a timestamp for there radio transmissions because there was a delay between sending and received (just like the satelite linkups they do on the news).
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9920720
>until sometime after .... zulu
sometime between then and
WHEN: Thu Dec 11 02:57:15 2003 (UTC)


>they used the zulu timezone as a timestamp
seems perfectly reasonable
0
 
LVL 2

Author Comment

by:davepusey
ID: 9921678
I am now accessing the site ok and dns dig shows correct information.

Now, who wants the points?
0
 
LVL 2

Author Comment

by:davepusey
ID: 9921853
Dumb question! I wil give then to chicagoan and he did the most work. I would normally do a split and give some to qwaletee but he made a bit a shambles of it by incorrectly spelling my name on the dns dig and confusing things.
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9922017
B?
0
 
LVL 31

Expert Comment

by:qwaletee
ID: 9923488
No, I deserve nothing.  Chicago knows loads more about this than I do, and what I contributed would have ben useful, only if you were pusey.co.uk

If I ever have a DNS issue, I am definitely going to chicago!
0
 
LVL 31

Expert Comment

by:qwaletee
ID: 9923502
FYI, GMT is not quite teh same thing as UTC.  GMT is the local time, which can be adjusted for DST if they wish, and is allowed to drift from the official time.  (Remember those leap seconds they have once in a while?  UTC corects for them as needed, not at teh end of the year.)
0
 
LVL 18

Expert Comment

by:chicagoan
ID: 9923849
qwaletee:
you were on the right track, you just dropped some bits from your paste buffer
0
 
LVL 31

Expert Comment

by:qwaletee
ID: 9924671
Chicagoan,

Well, I know enough to talk with someone like you, and I know the basics of whois and the concepts of how DNS works -- but the limit of my knowledge is basically:

the seven sisters
authoritative servers
referrals from non-authoritative servers
the different record types

But show me a dig trace, and I'll have to try to remember if I know what a dig trace is.  Ok, I know what a TTL is, but I wouldn't know how to find one.

Now, if I had a real DNS issue, I could probably learn all that stuff quickly enough to get me somewhere... but 'd probably ask you for help to start with.

Oh, yeah, and those bits were gray cells.  I typed it, and didn't check.  Duh!
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

I wrote this article to explain some important DNS concepts that should be known to avoid some typical configuration errors I often see in forums. I assume that what is described here is the typical behavior of Microsoft DNS client. I don't know …
I've written instructions for one router type, but this principle may be useful for others of the same brand and even other brands of router. Problem: I had an issue especially with mobile devices that refused to use DNS information supplied via…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now