Help - Search - Members - Calendar
Full Version: Subdomain help
The Planet Forums > System Administration > DNS Hosting
KennyM
Here is our current DNS entry:
CODE
$ORIGIN .
$TTL 43200
yourgamingsolution.com IN SOA ns1.theplanetdomains.com support.yourgamingsolution.com. (
2007120208 ; serial LAST:c30335thet
900 ; refresh period
900 ; retry period
1209600 ; expire period
86400) ; minimum TTL period

$ORIGIN yourgamingsolution.com.
yourgamingsolution.com. IN NS ns1.theplanet.com.
yourgamingsolution.com. IN NS ns2.theplanet.com.
yourgamingsolution.com. IN MX 1 ASPMX.L.GOOGLE.COM.
yourgamingsolution.com. IN MX 5 ALT1.ASPMX.L.GOOGLE.COM.
yourgamingsolution.com. IN MX 5 ALT2.ASPMX.L.GOOGLE.COM.
yourgamingsolution.com. IN MX 10 ASPMX2.GOOGLEMAIL.COM.
yourgamingsolution.com. IN MX 10 ASPMX3.GOOGLEMAIL.COM.
yourgamingsolution.com. IN MX 10 ASPMX4.GOOGLEMAIL.COM.
yourgamingsolution.com. IN MX 10 ASPMX5.GOOGLEMAIL.COM.
yourgamingsolution.com. IN A 208.109.158.238
www IN A 208.109.158.238
ftp IN A 208.109.158.238
mail IN A 208.109.158.238
test IN A 208.109.158.238
billing IN A 208.109.158.238
cortex IN A 208.109.158.238
portskis1 IN A 74.52.139.108
portskis2 IN A 74.52.139.109

The problem we're having is that for some people our subdomains don't resolve and for some they do. Does that DNS entry look right, or is something wrong?
James Jhurani
I must assume you made a change the the DNS... The changes need to finish propagating. I would wait 24-72 hours, and then if it still is not working, then worry about it. Although you may want to update the serial if you made a change.
KennyM
QUOTE (jjhurani @ Dec 9 2007, 05:29 PM) *
I must assume you made a change the the DNS... The changes need to finish propagating. I would wait 24-72 hours, and then if it still is not working, then worry about it. Although you may want to update the serial if you made a change.

No, I made the changes over a week ago and they still don't work for some people. The work fine for me, but for some other people I know they don't...Any more ideas?
Jeff
Can you have one of the people who can't reach your subdomain(s) do an nslookup (or dig) and send you the results to see what their ISP's dns server is returning for the subdomain. Are the people affected local using a common isp where a firewall or network issue or common ISP dns server/cache may be coming into play, or different providers?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.