Domain Name...
#1
Posted 09 June 2007 - 01:45 PM
Thanks,
FlameGuard
#2
Posted 09 June 2007 - 02:12 PM
C:\Documents and Settings\Bart van Heukelom>nslookup www.bfmexpansions.net *** Can't find server name for address 192.168.2.1: Non-existent domain *** Default servers are not available Server: UnKnown Address: 192.168.2.1 *** UnKnown can't find www.bfmexpansions.net: Non-existent domainso it's something with DNS, not Revora
Einstein: "We can’t solve problems by using the same kind of thinking we used when we created them."
#3
Posted 09 June 2007 - 03:17 PM
ns1.icetex-hosting.net
ns2.icetex-hosting.net
Command & Conquer Mods, Mods Support, Public Researchs, Map Archives, Tutorials, Tools, A Friendly Community and much more. Check it out now!
#4
Posted 09 June 2007 - 05:16 PM
#5
Posted 09 June 2007 - 06:00 PM
http://www.dnsstuff....eexpansions.net
#7
Posted 10 June 2007 - 01:40 PM
#8
Posted 10 June 2007 - 04:06 PM
Command & Conquer Mods, Mods Support, Public Researchs, Map Archives, Tutorials, Tools, A Friendly Community and much more. Check it out now!
#9
Posted 10 June 2007 - 04:46 PM
#10
Posted 10 June 2007 - 11:26 PM
I've compared your domain with mine (ppmsite.com)
http://www.dnsstuff....eexpansions.net
http://www.dnsstuff......n=ppmsite.com
As you may notice, the situation improved, but there are still some differences:
Error: At least one of your MX records points to an IP address that is not a public IP. The problem IP(s) are:
0.0.0.1 is not a public IP
Note that these IPs are not reachable, which can cause extra resource usage, slight mail delays, and possibly bounced mail.
Error: At least one of your WWW IPs is not a public IP. The problem IP(s) are:
0.0.0.1 is not a public IP
That means that some or all people trying to get to your web site will not be able to get there.
I wonder what is really pointing to 0.0.0.1 on your domain. MM fixed your DNS entry in our server, so I think that there is a big chance that it might be your problem.
Command & Conquer Mods, Mods Support, Public Researchs, Map Archives, Tutorials, Tools, A Friendly Community and much more. Check it out now!
#11
Posted 11 June 2007 - 12:36 AM
nameserver = DNSIt's the nameservers, not his DNS settings
er, yeah. I swear everything I write makes sense in my head
What I meant was that it was the nameservers themselves lacking the DNS records, and not his own DNS records on the domain registrar. The domain was properly pointed with NS records to the two nameservers, but the nameservers did not return records.
Edit: It's still not resolving. He properly points to the nameservers. And there is now DNS info returned. Here's the SOA:
Primary nameserver: ns1.icetex-hosting.net.
Hostmaster E-mail address: jmoe2008.gmail.com.
Serial #: 2007061001
Refresh: 86400
Retry: 7200
Expire: 3600000
Default TTL: 86400
Problem is, the A record returned by the nameservers points to 0.0.0.1
bfmeexpansions.net. A IN 14400 0.0.0.1
http://www.dnsstuff....2...et&type=ALL
Edited by Destroyer, 11 June 2007 - 12:44 AM.
#12
Posted 15 June 2007 - 03:20 AM
http://www.bfmeexpansions.net
Give it a try.
Command & Conquer Mods, Mods Support, Public Researchs, Map Archives, Tutorials, Tools, A Friendly Community and much more. Check it out now!
#13
Posted 15 June 2007 - 04:31 AM
#15
Posted 19 June 2007 - 03:45 PM
#16
Posted 19 June 2007 - 05:58 PM
#17
Posted 19 June 2007 - 07:18 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users