On Wed, Feb 08, 2012 at 12:14:03PM +0000, john lewis wrote:
I am also having problems resolving domain names
root@benden: /home/jayell # dig startx.co.uk
[snip]
;; ANSWER SECTION:
startx.co.uk. 41140 IN A 212.13.194.129
You've got about 12 hours still to go on the TTL for this record.
;; AUTHORITY SECTION:
startx.co.uk. 41140 IN NS ns0.zen.co.uk.
startx.co.uk. 41140 IN NS ns1.zen.co.uk.
;; ADDITIONAL SECTION:
ns0.zen.co.uk. 4966 IN A 212.23.8.1
ns1.zen.co.uk. 4910 IN A 212.23.3.1
I am unable to ssh johnlewis(a)startx.co.uk getting this
error
ssh: connect to host startx.co.uk port blah: No route to host
Yes, because it's pointing at the wrong IP address right now.
I can ssh johnlewis(a)85.119.82.129
and I can access the console with
ssh startx(a)startx.console.bitfolk.com
so could reboot if need be.
Wouldn't help.
I can access my websites by using IP addresses rather
than domain names
and have advised my regular users to do so for now but "casual"
enquirers will not know the IP address.
Can I assume that the domain names will get resolved in a few hours or
thereabouts or do I need to do something else to get this working.
/etc/resolvconf has
search co.uk
nameserver 85.119.80.222
nameserver 85.119.80.232
which are the Bitfolk DNS addresses I think
If you do:
$ dig @ns0.zen.co.uk startx.co.uk.
$ dig @ns1.zen.co.uk startx.co.uk.
then you will see that you're still publishing 212.13.194.129 as the
IP address for your domain from your autoritative servers
(ns0.zen.co.uk and ns1.zen.co.uk). You need to fix this -- probably
via some kind of control panel app at Zen. Approximately 24 hours
after you fix the records at Zen, everyone should have got the right
records again.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk |
darksatanic.net | lug.org.uk ===
PGP key: 515C238D from
wwwkeys.eu.pgp.net or
http://www.carfax.org.uk
--- The trouble with you, Ibid, is you think you know everything. ---