Ubuntu Server, ISPConfig, Domain name, and problems

NYCSavage · Nov 25, 2009

Hi, new to Ubuntu and really struggling here

I have 7 websites on my current HostGator account and decided to host myself as they are low traffic sites and I am using my office cable connection

As a trial, I changed the Nameserver to point at ns1.mysite.co.uk which points to my office IP and ms2.mysite.co.uk which then points to my static home IP

I setup a base unit with Ubuntu Server 9.10 using The Perfect Server - Ubuntu 9.10 [ISPConfig 3] and when I enter my IP into IE I get the "It Works" screen.

I setup ISPConfig3 by reading posts here on the forums and yet I am still having problems.

I waited 48 hours and entered mysite.co.uk into the IE browser and I get the "Internet Explorer cannot display the webpage" screen.

Can anyone help?

falko · Nov 25, 2009

Did you check your domain on www.intodns.com ?

NYCSavage · Nov 25, 2009

Makes no sense to me lol

Parent Domain NS records Nameserver records returned by the parent servers are:

ns2.123-reg.co.uk. ['92.51.159.40'] (NO GLUE) [TTL=172800]
ns.123-reg.co.uk. ['212.67.202.2'] (NO GLUE) [TTL=172800]

ns1.nic.uk was kind enough to give us that information.
TLD Parent Check Good. ns1.nic.uk, the parent server I interogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check.
Your nameservers are listed Good. The parent server ns1.nic.uk has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
DNS Parent sent Glue The parent nameserver ns1.nic.uk is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happends a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.)
Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.
NS NS records from your nameservers NS records got from your nameservers listed at the parent NS are:

ns2.hosteurope.com ['92.51.159.40'] [TTL=257]
ns.hosteurope.com ['212.67.202.2'] [TTL=257]
Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Same Glue The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below!
Glue for NS records OK. When I asked your nameservers for your NS records they also returned the A records for the NS records. This is a good thing as it will spare an extra A lookup needed to find those A records.
Mismatched NS records OK. The NS records at all your nameservers are identical.
DNS servers responded Good. All nameservers listed at the parent server responded.
Name of nameservers are valid OK. All of the NS records that your nameservers report seem valid.
Multiple Nameservers Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
Missing nameservers reported by parent FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!
ns.hosteurope.com
ns2.hosteurope.com
Missing nameservers reported by your nameservers ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns.123-reg.co.uk
ns2.123-reg.co.uk
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).
Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Different subnets OK. Looks like you have nameservers on different subnets!
IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and usefull even if UDP connections are used by default.
Different autonomous systems OK. It seems you are safe from a single point of failure. You must be carefull about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
Stealth NS records sent Ok. No stealth ns records are sent
SOA SOA record The SOA record is:
Primary nameserver: ns.hosteurope.com
Hostmaster E-mail address: hostmaster.***.co.uk
Serial #: 2009112502
Refresh: 86400
Retry: 3600
Expire: 1209600 2 weeks
Default TTL: 257
NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 2009112502.
SOA MNAME entry WARNING: SOA MNAME (ns.hosteurope.com) is not listed as a primary nameserver at your parent nameserver!
SOA Serial Your SOA serial number is: 2009112502. This appears to be in the recommended format of YYYYMMDDnn.
SOA REFRESH OK. Your SOA REFRESH interval is: 86400. That is OK
SOA RETRY Your SOA RETRY value is: 3600. Looks ok
SOA EXPIRE Your SOA EXPIRE number is: 1209600.Looks ok
SOA MINIMUM TTL Your SOA MINIMUM TTL is: 257. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommands a value of 1-3 hours. Your value of 257 is OK.
MX MX Records Your MX records that were reported by your nameservers are:

10 mail.***.co.uk No A Record (no glue either)

[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
Different MX records at nameservers Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
MX name validity Good. I did not detect any invalid hostnames for your MX records.
MX IPs are public OK. All of your MX records appear to use public IPs.
MX CNAME Check OK. No problems here.
MX A request returns CNAME OK. No CNAMEs returned for A records lookups.
MX is not IP OK. All of your MX records are host names.
Number of MX records OK. Looks like you only have one MX record at your nameservers. You should be carefull about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time.
Mismatched MX A OK. I did not detect differing IPs for your MX records.
Duplicate MX A records OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
Reverse MX A records (PTR) Your reverse (PTR) record:
You have reverse (PTR) records for all your IPs, that is a good thing.
WWW WWW A Record Your www.***.co.uk A record is:
www.***.co.uk [94.168.29.32]
IPs are public OK. All of your WWW IPs appear to be public IPs.
WWW CNAME OK. No CNAME
Click to expand...

falko · Nov 26, 2009

ns2.123-reg.co.uk. ['92.51.159.40'] (NO GLUE) [TTL=172800]
ns.123-reg.co.uk. ['212.67.202.2'] (NO GLUE) [TTL=172800]
Click to expand...

The domain's using your registrar's nameservers instead of your own nameservers.

NYCSavage · Nov 26, 2009

I did change them back after a few days as it wasnt working with my own nameservers

falko · Nov 27, 2009

These tutorials (although for ISPConfig 2) should give you the idea what you have to do to run your own nameservers:

http://www.howtoforge.com/ispconfig_dns_godaddy
http://www.howtoforge.com/ispconfig_dns_providerdomain_schlund

Log in or Sign up

Ubuntu Server, ISPConfig, Domain name, and problems

NYCSavage New Member

falko Super Moderator Howtoforge Staff

NYCSavage New Member

falko Super Moderator Howtoforge Staff

NYCSavage New Member

falko Super Moderator Howtoforge Staff

Share This Page

Log in or Sign up

Ubuntu Server, ISPConfig, Domain name, and problems

NYCSavage New Member

falko Super Moderator Howtoforge Staff

NYCSavage New Member

falko Super Moderator Howtoforge Staff

NYCSavage New Member

falko Super Moderator Howtoforge Staff

Share This Page

Useful Searches