DNS Problem...

Dev Shed Forums Sponsor:

December 18th, 2001, 04:06 PM

vboyz103

Junior Member

Join Date: Dec 2001

Posts: 14

Time spent in forums: < 1 sec
Reputation Power: 0

DNS Problem...

Hi, all! I got a quick question. I am hosting some web pages with users signed up and I make their web page to be like http://usersname.mydomain.com and for some reason sometimes they can hit the web page, and sometimes they can't. I check the message log and I saw some "lame servers on ...." entries. SO is it why?? Is this DNS problem at all? If so, can you pin point me to a solution?

Thanks!!

December 18th, 2001, 09:48 PM

freebsd

Contributing User

Join Date: Jan 2001

Posts: 5

Time spent in forums: < 1 sec
Reputation Power: 0

>> lame servers on ...." entries. SO is it why??

You believe your authoritative DNS server is authoritative for username.mydomain.com but it's not.

>> can you pin point me to a solution?

Show us your unedited zone file.

December 18th, 2001, 10:49 PM

vboyz103

Junior Member

Join Date: Dec 2001

Posts: 14

Time spent in forums: < 1 sec
Reputation Power: 0

Thanks...

Thanks for the reply and here it is my zone file...

$TTL 8600
@ IN SOA mydomain.com root.mydomain.com. (
200109206 ; serial, todays date + todays serial #
8H ; refresh, seconds
2H ; retry, seconds
4W ; expire, seconds
1D ) ; minimum, seconds
NS ns1.mydomain.com.
MX 10 mail.mydomain.com.

mydomain.com. A 12.x.x.x

localhost A 127.0.0.1
mirror A X.X.X.X //Different address

ftp CNAME mydomain.com.
mail CNAME mydomain.com.
www CNAME mydomain.com.

;;; Other Hosting

user1 A 12.X.X.X //my main static IP.
user2 A 12.X.X.X
user3 A 12.X.X.X

The clients user1-user3 sometimes having difficulty of access their web page at http://user1.mydomain.com and so as the others.

December 18th, 2001, 11:21 PM

freebsd

Contributing User

Join Date: Jan 2001

Posts: 5

Time spent in forums: < 1 sec
Reputation Power: 0

As I said, don't use CNAME, use multiple A record instead. You also have an important A record missing, the ns1.mydomain.com itself. Don't set your MX to mail.mydomain.com, it's extremely unreliable. Set your MX to point to ns1.mydomain.com. Your SOA was incorrect, it should point to ns1.mydomain.com.
It's easily said than done so here comes the example:

Code:

$TTL 86400
mydomain.com.	IN	SOA	ns1.mydomain.com.	hostmaster.mydomain.com.	(
				20011218 ; serial
				8H ; refresh, seconds
				2H ; retry, seconds
				3D ; expire, 4W too long
				1D ); minimum, seconds 
mydomain.com.		IN	NS	ns1.mydomain.com.
ns1.mydomain.com.	IN	A	12.34.56.78
mirror.mydomain.com.	IN	A	78.65.43.21
www.mydomain.com.	IN	A	12.34.56.78
ftp.mydomain.com.	IN	A	12.34.56.78
mydomain.com.		IN	A	12.34.56.78
mydomain.com.		IN	MX	0	ns1.mydomain.com.
*.mydomain.com.		IN	A	12.34.56.78

Last edited by freebsd : December 19th, 2001 at 03:08 PM.

December 19th, 2001, 02:53 AM

vboyz103

Junior Member

Join Date: Dec 2001

Posts: 14

Time spent in forums: < 1 sec
Reputation Power: 0

Thanks...

Thanks much, this will save me on the fact of hosting virtual host...you are da man...

Developer Shed Advertisers and Affiliates