Fajar and Tim Thank you so much for very details and excellent replies.. Tim, yes, i also want to do ftp server, mail services, apache, mySql and phpMyadmin.. i will follow your suggestions.. I appreciate your concerns from all aspects. i will test with different names like dns.test. I have found portforward.com for using dhcp with adsl modem from home. hopefully i can make it work from home.. This list has been a huge help for me.. Cheers. On 10/11/05, Tim <ignored_mailbox@xxxxxxxxxxxx> wrote: > On Mon, 2005-10-10 at 03:50 +1000, Maung Nanda Linn Aung wrote: > > > Okay, at least you didn't pick a currently in-use domain, but it might > be used by someone, at some stage in the future. It's not a good idea > to invent domains. There are some reserved domain names that you can > use without causing problems for anyone else: localhost, test, > invalid, and example.com. You'd use them as top-level domains. > > e.g. my-pc.test and your-pc.test > > Test is probably the best to use. Trying to use localhost can be a > problem on some systems (they always want to use it as 127.0.0.1), using > invalid will give you grief if you want to test mail (many servers are > set to not post to it), example.com is there for examples and can be > used without bothering other people, but it might give you grief as > there are public DNS records for it already. > > > I get a similar result. It means the DNS server you queried (the one > three lines above [SERVER: 192.168.116.2#53(192.168.116.2)] didn't have > the answer, and expected the Australian registrar (.com.au.) to have the > answer, and it didn't. > > Now, this means that if you've tried creating a local record for that > domain, you haven't succeeded. Probably, you need to restart your DNS > server to make it notice a changed record, though I think the new GUI > tool manages all of that for you. > > Or that you should be asking *your* local DNS test server instead of the > normal DNS server for your network. You can make dig query a specific > DNS server by putting its address in your query after the @ sign. > > e.g. dig my-pc.test @127.0.0.1 > > > Which looks *mostly* okay. > > After SOA you've got www.genitech.com.au twice. The first one should be > your name server address, the second one the e-mail address for the DNS > record manager (with the first unescaped dot representing the @ sign, > because the @ sign has other meanings in the DNS records). > > e.g. @ IN SOA ns.test. hostmaster.test. ( > > Would specify ns.test. as the authoritative name server, > and <hostmaster@test> as the contact address (hostmaster being > the customary address for this sort of thing). > > It's customary to have an MX record for a domain, giving the mailserver > address for any mail to it. In its absence it may be presumed, but I > wouldn't rely on that. > > e.g. Under your NS record, include an MX record, something like this: > > IN NS ns.test. > MX 1 mail.test. > > Though this isn't going to matter if you're not going to test any mail > system on that domain, and the domain is only for internal use. > > You've got two different A records for the www subdomain, so expect to > get different answers to some queries for its IP address. > > By the way, there's a convention of naming your DNS server as the ns > subdomain of your domain. e.g. ns.test. Of course you can call it > "dns.test.", it's up to you, but it's usually best to follow the norms. > > NB: Read the guides about putting trailing dots, or omitting them, in > the right places if you don't already know about that. Simply put, > without the trailing dot, it's presumed to be a sub-domain, and will get > your domain prepended to it. With the dot, it's presumed to be a > fully-qualified domain name, and will be used, as-is. > _________________________________ > > "allow-update" with "none" and some addresses to allow updates sounds a > bit contradictory to me, but I'm not looking at the manuals at the > moment. > > > Well you can do as much as you want to, within your own network. Not > sure about what you can beyond that. I don't know whether dodo allows > servers, and even if they do, they wouldn't be happy if you set > something up badly. > > If you own domain names, then do what you like with them with your > configuration testing. If you use them on the internet but want to do > internal testing without conflicts, use a subdomain internally. > > e.g. If you happened to own example.com and used it on the net, as > example.com and www.example.com you could use lan.example.com at home, > so your internal testing queries wouldn't get muddled with outside > records. > > -- > Don't send private replies to my address, the mailbox is ignored. > I read messages from the public lists. > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Best Regards, Linn nandalinnaung@xxxxxxxxx
