Hi all,
The problem has probably been fixed by DNS propagation (I think), but I'd still like to know if there are side-effects of the things I did. So the original data has been quoted for your information. Thanks.
Thanks
The problem has probably been fixed by DNS propagation (I think), but I'd still like to know if there are side-effects of the things I did. So the original data has been quoted for your information. Thanks.
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
Last edited: