Probleem met DNS

[frvge]

Is gefixed door DNS propagation denk ik, maar ik weet niet zeker of er nog side-effects zijn van de dingen die ik heb gedaan.
Orginele post is gequote.

kopietje van mijn post @ Directadmin forum. Heb Site Check van WHT gebruikt, en alles lijkt in orde. Onder aan zijn nog extra traceroutes toegevoegd (reasonnet/tiscali)

Hi all,

The IP of ns1.sanbax.com 85.92.145.32 isn't responding when I ping. It's possible that it's because of some problem with my ISP, but I can access ns2.sanbax.com (85.92.145.33).

First of all, ns2.sanbax.com was set up to point to server5 ( .43). This made me confused and I edited it back to .33 , but now I think it's because of fall-back DNS in case server1 goes down, so it's now pointing again to .43 (this all with the domain registry).

In my 'enthusiam' I restarted the network with service network restart, but after that I couldn't ping ns2 at all.

I did
ifconfig eth1 up
ifconfig eth1
ifconfig eth1 85.92.145.33
ifconfig eth0 85.92.145.32

and so .33 is pingable again. However, .32 still is not.

2 questions:
- Does sanbax.com and/or pinging 85.92.145.32 work for you?
- Did I screw something that was working correctly up with my actions and how do I restore it?

I can access all other IPs. I have access to server1 (.32) via another server.
Firewalls (iptables and APF) have been flushed and stopped.
I suck with DNS, but my more competent partner is having a vacaction.

Thanks

----

Van server1 naar tiscali geeft problemen

[root@server1 ~]# traceroute tiscali.nl
traceroute to tiscali.nl (195.241.78.68), 30 hops max, 38 byte packets
1 85-92-145-4.pcextreme.nl (85.92.145.4) 0.602 ms 0.702 ms 35.591 ms
2 89-18-191-29.pcextreme.nl (89.18.191.29) 0.353 ms 0.351 ms 0.363 ms
3 89-18-191-102.reasonnet.com (89.18.191.102) 0.487 ms 0.354 ms 0.364 ms
4 89-18-191-54.reasonnet.com (89.18.191.54) 4.485 ms 0.728 ms 0.613 ms
5 * * *
6 vpn10-inet.bcsw3.asd-hp.net.tiscali.nl (195.241.57.1) 1.369 ms 1.335 ms 1.236 ms
7 * vlan206.ds2.hp1.net.tiscali.nl (195.241.78.78) 1.532 ms !X *
8 vlan206.ds2.hp1.net.tiscali.nl (195.241.78.78) 1.429 ms !X * *
9 * vlan206.ds2.hp1.net.tiscali.nl (195.241.78.78) 1.531 ms !X *
10 vlan206.ds2.hp1.net.tiscali.nl (195.241.78.78) 1.427 ms !X


van huis naar server:
C:\Documents and Settings\Gebruiker>tracert sanbax.com
Bezig met het traceren van de route naar sanbax.com [85.92.145.32]
via maximaal 30 hops:
1 <1 ms <1 ms <1 ms tiscali-modem [192.168.1.254]
2 19 ms 19 ms 19 ms 82-171-143-254.dsl.ip.tiscali.nl [82.171.143.254
]
3 20 ms 20 ms 21 ms vpn181-tisadsl.bcsw1.asd-nh.net.tiscali.nl [195.
241.3.25]
4 21 ms 21 ms 21 ms vlan507.bcsw1.asd-tc2.net.tiscali.nl [195.241.4.
54]
5 21 ms 21 ms 20 ms nikhef.openpeering.nl [195.69.144.189]
6 21 ms 21 ms 21 ms openpeering-2.reasonnet.com [82.150.153.194]
7 21 ms 22 ms 20 ms 89-18-191-17.reasonnet.com [89.18.191.17]
8 * * * Time-out bij opdracht.


Maar dat komt dan waarschijnlijk omdat de .32 niet werkt oid.


Tips welkom.

[IT-worX]

Tracert vanuit Telenet:

C:\Documents and Settings\Krisken>tracert sanbax.com

Bezig met het traceren van de route naar sanbax.com [85.92.145.32]
via maximaal 30 hops:

1 <1 ms <1 ms <1 ms 10.253.0.1
2 8 ms 6 ms 6 ms 10.64.64.1
3 8 ms 7 ms 9 ms dD5E0FB42.access.telenet.be [213.224.251.66]
4 7 ms 8 ms 8 ms dD5E0FD4D.access.telenet.be [213.224.253.77]
5 9 ms 9 ms 13 ms dD5E0FD19.access.telenet.be [213.224.253.25]
6 14 ms 11 ms 10 ms dD5E0FD15.access.telenet.be [213.224.253.21]
7 9 ms 9 ms 9 ms dD5E0FD9A.access.telenet.be [213.224.253.154]
8 11 ms 12 ms 10 ms kpn.bnix.net [194.53.172.59]
9 11 ms 12 ms 11 ms zvtm-s1-rou-1041.BE.eurorings.net [134.222.230.1
49]
10 26 ms 14 ms 15 ms asd2-rou-1021.NL.eurorings.net [134.222.230.9]
11 15 ms 18 ms 15 ms asd-s4-rou-1001.NL.eurorings.net [134.222.230.20
6]
12 15 ms 16 ms 15 ms 134.222.129.6
13 15 ms 15 ms 16 ms jointtransit.reasonnet.com [217.170.9.91]
14 16 ms 17 ms 16 ms 89-18-191-101.reasonnet.com [89.18.191.101]
15 15 ms 72 ms 16 ms 89-18-191-30.pcextreme.nl [89.18.191.30]
16 16 ms 17 ms 16 ms server1.sanbax.com [85.92.145.32]

De trace is voltooid.

Tracert vanuit Scarlet:

traceroute to www.sanbax.com (85.92.145.32), 30 hops max, 40 byte packets
1 193.34.88.1 (193.34.88.1) 0.450 ms 0.209 ms 0.220 ms
2 gig0-0-0-100.inx-dr01.ias.scarlet.be (194.119.224.54) 0.730 ms 0.719 ms 0.729 ms
3 realroot.bnix.net (194.53.172.83) 0.731 ms * 0.979 ms
4 te-4-1.bb1.bru2.be.gbxs.net (83.143.243.6) 5.222 ms * 5.699 ms
5 ge-2-1.bb2.bru2.be.gbxs.net (83.143.241.14) 5.726 ms 5.475 ms 5.473 ms
6 so-7-0-0-0.bb1.ams3.nl.gbxs.net (83.143.243.18) 5.225 ms 5.216 ms 5.231 ms
7 Rokscom.ge-6-1-0-403.bb1.ams3.nl.gbxs.net (193.27.64.94) 7.479 ms 7.713 ms 7.733 ms
8 89-18-191-22.reasonnet.com (89.18.191.22) 7.225 ms 7.464 ms 7.484 ms
9 89-18-191-25.reasonnet.com (89.18.191.25) 7.726 ms 7.721 ms 7.479 ms
10 89-18-191-101.reasonnet.com (89.18.191.101) 7.478 ms 7.711 ms 7.731 ms
11 89-18-191-30.pcextreme.nl (89.18.191.30) 8.231 ms 8.213 ms 7.985 ms
12 server1.sanbax.com (85.92.145.32) 7.975 ms 7.220 ms 7.722 ms

[frvge]

Had een probleem kunnen zijn met KPN (=Tiscali) want daar was iets mis las ik op nu.nl . Alles lijkt opgelost en we hopen er maar het beste van. Slotje graag