frvge
27/07/07, 13:26
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. :lovewht:
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. :lovewht: