This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.
but at webmin / Networking - Network Configuration - Hostname and DNS Client it still just says ns1 and when i replace it with ns1.flirtsnflings.com and save then go back in it returns to just ns1
Hmmm, you're right. Looks like Webmin is just giving back the short name. So command line is the only reliable way to know.
From the command line its fine so lets get onto the rest of the process
Yep, if the command line says it's so, then it's so.
as I said in my question above what about these isp ip addresses i require?
the IP's you should already have. They are from your VPS provider as explained in the pics as well. You'll probably find them in the module (see image)
on a note. your nameservers are not registered, They have A records. The difference of this setting is that a request will go over GoDaddy's nameserver instead of asking the root servers. the requests therefore take a bit longer
it is not a problem to worry about now as your nameservers will work.
GoDaddy (unlike some registrars) makes it really hard to bootstrap a name server into existence. You have to first have a working zone on a name server that already exists, which knows about your new name servers. It's irritating, but you only have to do it once.
So, for example, if I wanted to create ns0.virtualmin.com, I would have to first setup the virtualmin.com zone on a name server that GoDaddy already accepts as existent (one of their own name servers, or some other free name service will work fine), and create an A record for ns0.virtualmin.com pointing to my new server.
Then, and only then, could I tell GoDaddy about the new name server by filling in the name ns0.virtualmin.com.
Make sense? In short, GoDaddy doesn't let you say, "I want a name server with the name ns0.virtualmin.com on the IP address 192.168.1.1". It only lets you say, "I want a name server with the name ns0.virtualmin.com" and that name has to already resolve out on the Internet.
look in my image and compare to yours. there should be the 127.0.0.1 and 2 IP's you dont know.
those two IP's belong to your provider and is used to find your box in their network. I am assuming this already works. I also have a vps somewhere and its the same situation as with my dedicated server.
in the network interface I don't think its absolutely necessary to add the second IP on a virtual interface eth0:1 but I did it none the less.
once that's done the system should work as expected. Hope I dont forget anything.
the next step is to create a new server in virtualmin, make it flirtsnflings.com so you can satisfy godaddy and get your nameservers bootstrapped into the world servers. I love namecheap.com for making life so easy.
LOL lets prey it works. That was like pulling teeth I was almost ready to go back to shared hosting or paying an extra £10 month for cpanel to be installed.
Thanks for your help if all is well I will try and make up some sort of step by step how to from this thread then post it here for other clueless wanders.
or paying an extra £10 month for cpanel to be installed
So...umm...you know that cPanel also can't make this issue with GoDaddy just go away, right? Virtualmin actually does quite a bit more than cPanel does, but none of us have the ability to make your registrar aware of your domain servers. This just not within the purview of your control panel.
the pulling teeth feelings comes when you walk in the dark. When I first started I had the same and took a long time before a saw the light. Once it sinks in, it's actually pretty easy too get stuff working the way you want.
Later you have to look again at the annoying way godaddy handles the nameservers so the requests will go faster and you can create A records as glue on your server.
you're not totally done but at least it will work. Fine-tuning will come.
Well I put A records in as well just exaclty how it was done in that how to I showed you. Perhaps only the A records have propagated so far? as these seem to work fast with godaddy. Otherwise I am going to ask godaddy support exactly how it should be done.
Ill wait till I get a website up and running before fine tuning.
So, either you haven't changed it correctly at GoDaddy, or it hasn't yet been updated in the root servers yet. It can take an hour or two to show up.
To be clear: Nothing is expected to work right now, unless you've added A records to GoDaddy's name servers. Your name server is not even in the picture yet, because your glue records at GoDaddy do not yet point to your server.
I changed the total dns records as shown in the screen1. I but I never changed the namesever settings in the normal domain control interface as shown in screen 2 I take it these should be set to my nameservers?
I wasn't sure If i had to do that since the domain its self was registered as a nameserver.
An NS record and a glue record are not the same thing. You're kinda conflating the two different services GoDaddy is providing for you in this scenario.
One service is registrar. This simply tells the world what name servers are authoritative for your zone, and how to contact the administrator and such.
The other service is name service. The two are orthogonal. Creating an NS record is merely adding records to the zone within the GoDaddy DNS server. It is not modifying or in any way interacting with the glue records that GoDaddy is feeding into the root name servers.
Name service and domain registration are two distinct services.
yes it is now correct, but it hasn't fully propagated yet.
you see the request is from root and your nameservers instead of godaddy's
7.1% of queries will be returned by 192.5.6.30 (A.GTLD-SERVERS.NET) - answer was not authoritative flirtsnflings.com. 172800 IN NS ns1.flirtsnflings.com.
flirtsnflings.com. 172800 IN NS ns2.flirtsnflings.com.
And
7.7% of queries will be returned by 192.5.6.30 (A.GTLD-SERVERS.NET) - answer was not authoritative ns1.flirtsnflings.com. 172800 IN A 94.76.201.163
to make it simple,
for every domain hosted on your server you need to change the ns records at GoDaddy to point to your nameservers ns1.flirtsnflings.com and ns2.flirtsnflings.com.
Again, changing NS records for a domain and registering nameservers are two very different things.
So when creating a new virtual server in virtualmin, All i need to do is create the virtual server give it the name of the domain and then point my domain in go daddy to my nameservers? Nothing else?
I added joomlaplazza.com as a virtual server and pointed its nameserver to mine and its working but Im still having issues with the mail. It finds the mail.joomlaplazza.com but wont authentic even though i no the password is correct.
your nameservers are okay.
Some settings on your machine are not, i.e. hostname shows only ns1
Therefore some stuff breaks.
joomlaplazza.com is set up correctly but some settings in the BIND module are not yet correct..
webmin - servers - BIND DNS Server - right pane click at the top on Module config - dropdown choose Zone file options - at Default master server for master zones fill in ns1.flirtsnflings.com - at Serial number style Select Date based - click save
Now: webmin - servers - BIND DNS Server - right pane click Zone defaults.
click on the maser zone file for that domain.
Click on Address
In the field for Name fill in ns1.flirtsnflings.com. (with dot at end)
In the field Address fill in 94.76.201.163
Repeat for ns2.flirtsnflings.com.
Click save.
Oh and you should set the zone files to Date Based. Thats under Module Config - Zone file options in the dropdown and the the first option at the top.
I don't know. Im not familiar too much with the way Debian sets its stuff up, but Im sure its something simple.
If you have to go out you could create a temporary webmin user with access to the Virtualmin Virtual Servers, BIND DNS Server, Network Configuration, File Manager modules so i'll take a look and check on that.
send it to tech [at][ izicart [dot] com if you want me to have a look.
I edited the hosts file as suggested and now postfix has gone down with this error
Failed to query Postfix config command to get the current value of parameter : /usr/sbin/postconf: warning: valid_hostname: invalid character 32(decimal): ns1.flirtsnflings.com /usr/sbin/postconf: fatal: unable to use my own hostname
I needed to adjust the zone settings for the already created domains and some other minor details. Newly created domains will have all the correct settings (as long as your hostname file doesn't change)
Then I needed to set the hostname for Postfix so that is now also working again. I commented out #myorigin as this usually is a cause for trouble.
I assume you don't use Proftp since no domain is set up to use it.
Now you can fine-tune Apache and secure the server a bit more.
oh yeah I almost forgot. this: "127.0.0.1 andy91 localhost localhost.localdomain" I have changed to "127.0.0.1 localhost.localdomain, localhost" which makes a bit more sense
Proftp is the default ftp server but you can use vsftp as well. At the moment proftp is not running and no domain is configured to use it. If you want to use ftp then you have to configure your domains to use it. Else have ssh and sftp (port 22) into the server which is safer.
I thought ftp was setup automatically on each domain in virtualmin? Yeah I do want ftp working so im going to have to try and configure that.
I have mail.joomlaplazza.com setup as the outgoing server but its not authenticating. I can receive incoming mails but not sent outgoing. It should be set up as the same password right? Any idea whats going on their?
but at webmin / Networking - Network Configuration - Hostname and DNS Client it still just says ns1 and when i replace it with ns1.flirtsnflings.com and save then go back in it returns to just ns1
Hmmm, you're right. Looks like Webmin is just giving back the short name. So command line is the only reliable way to know.
From the command line its fine so lets get onto the rest of the process
Yep, if the command line says it's so, then it's so.
as I said in my question above what about these isp ip addresses i require?
I have no idea what you're asking.
--
Check out the forum guidelines!
the IP's you should already have. They are from your VPS provider as explained in the pics as well. You'll probably find them in the module (see image)
on a note. your nameservers are not registered, They have A records. The difference of this setting is that a request will go over GoDaddy's nameserver instead of asking the root servers. the requests therefore take a bit longer
it is not a problem to worry about now as your nameservers will work.
hmm thats only way I can see to register them at godaddy?
there is IP addresses already in the boxes but I dont no if they are correct or not the first one is
217.112.xxx.xxx
GoDaddy (unlike some registrars) makes it really hard to bootstrap a name server into existence. You have to first have a working zone on a name server that already exists, which knows about your new name servers. It's irritating, but you only have to do it once.
So, for example, if I wanted to create ns0.virtualmin.com, I would have to first setup the virtualmin.com zone on a name server that GoDaddy already accepts as existent (one of their own name servers, or some other free name service will work fine), and create an A record for ns0.virtualmin.com pointing to my new server.
Then, and only then, could I tell GoDaddy about the new name server by filling in the name ns0.virtualmin.com.
Make sense? In short, GoDaddy doesn't let you say, "I want a name server with the name ns0.virtualmin.com on the IP address 192.168.1.1". It only lets you say, "I want a name server with the name ns0.virtualmin.com" and that name has to already resolve out on the Internet.
--
Check out the forum guidelines!
thanks for that ronald so just ns1 in the hostname box was right after all LOL !
I added in the ns2 as shown in the host addresses screen shot
in network interfaces its eth0 in my system and both my ips are showing so do I need to add anything in here?
So for the ISP's IP's I need to ask them for the IP addresses of the nameservers for the server that is holding my VPS?
look in my image and compare to yours. there should be the 127.0.0.1 and 2 IP's you dont know.
those two IP's belong to your provider and is used to find your box in their network. I am assuming this already works. I also have a vps somewhere and its the same situation as with my dedicated server.
in the network interface I don't think its absolutely necessary to add the second IP on a virtual interface eth0:1 but I did it none the less.
yes there is two ip addresses I don't know! I wasn't sure if they were correct
so far the Hostname and DNS Client section looks ok
and network interface
so next
next is to tell virtualmin about the ns2. in the server template, see my previous 2 post on how/where to do that.
ok so in Bind DNS domian I put exactly this in the box:
"${DOM}. 38400 IN NS ns2.flirtsnflings.com" no dot at the end of .com
what now?
yes you need a dot at the end of that line! it has a reason.
once that's done the system should work as expected. Hope I dont forget anything.
the next step is to create a new server in virtualmin, make it flirtsnflings.com so you can satisfy godaddy and get your nameservers bootstrapped into the world servers. I love namecheap.com for making life so easy.
off the get some sleep.
ok so if I create a virtual server and point a domain to my nameservers it will all work even the email for the domains and everything?
that was the whole idea was it not :) so yes (if no other misconfigurations are on your server)
creating another domain is okay but give it time to propagate. I would first create flirtsnflings.com as that should work immediately.
LOL lets prey it works. That was like pulling teeth I was almost ready to go back to shared hosting or paying an extra £10 month for cpanel to be installed.
Thanks for your help if all is well I will try and make up some sort of step by step how to from this thread then post it here for other clueless wanders.
thanks mate.
or paying an extra £10 month for cpanel to be installed
So...umm...you know that cPanel also can't make this issue with GoDaddy just go away, right? Virtualmin actually does quite a bit more than cPanel does, but none of us have the ability to make your registrar aware of your domain servers. This just not within the purview of your control panel.
--
Check out the forum guidelines!
the pulling teeth feelings comes when you walk in the dark. When I first started I had the same and took a long time before a saw the light. Once it sinks in, it's actually pretty easy too get stuff working the way you want.
Later you have to look again at the annoying way godaddy handles the nameservers so the requests will go faster and you can create A records as glue on your server.
you're not totally done but at least it will work. Fine-tuning will come.
so dont forget to put the dot in that 1 line!
Well I put A records in as well just exaclty how it was done in that how to I showed you. Perhaps only the A records have propagated so far? as these seem to work fast with godaddy. Otherwise I am going to ask godaddy support exactly how it should be done.
Ill wait till I get a website up and running before fine tuning.
so its ${DOM}. 38400 IN NS ns2.flirtsnflings.com.
not
${DOM}. 38400 IN NS ns2.flirtsnflings.com
well I created the virtual host http://flirtsnflings.com/ but it doesnt work however http://ns1.flirtsnflings.com/ seems to point to the root of my server not the root of my virtual server.
GoDaddy isn't showing your name server(s) as being authoritative for this zone:
[joe@delilah ~]$ whois flirtsnflings.com
...
Domain servers in listed order:
NS25.DOMAINCONTROL.COM
NS26.DOMAINCONTROL.COM
So, either you haven't changed it correctly at GoDaddy, or it hasn't yet been updated in the root servers yet. It can take an hour or two to show up.
To be clear: Nothing is expected to work right now, unless you've added A records to GoDaddy's name servers. Your name server is not even in the picture yet, because your glue records at GoDaddy do not yet point to your server.
--
Check out the forum guidelines!
Do you know the godaddy Total DNS interface Joe?
I changed the total dns records as shown in the screen1. I but I never changed the namesever settings in the normal domain control interface as shown in screen 2 I take it these should be set to my nameservers?
edit screen1 was wrong it should be this one now
I used this to figure out how to do it
http://www.howtoforge.com/ispconfig_dns_godaddy
Yeah, those screenshots look sane as a starting point. And they seem to resolve OK for me:
[joe@delilah ~]$ host ns1.flirtsnflings.com
ns1.flirtsnflings.com has address 94.76.201.163
[joe@delilah ~]$ host ns2.flirtsnflings.com
ns2.flirtsnflings.com has address 94.76.201.164
--
Check out the forum guidelines!
yeah I think it was because I hadn't changed the the nameserver settings from
NS25.DOMAINCONTROL.COM NS26.DOMAINCONTROL.COM
to my nameservers
I wasn't sure If i had to do that since the domain its self was registered as a nameserver.
I wasn't sure If i had to do that since the domain its self was registered as a nameserver.
An NS record and a glue record are not the same thing. You're kinda conflating the two different services GoDaddy is providing for you in this scenario.
One service is registrar. This simply tells the world what name servers are authoritative for your zone, and how to contact the administrator and such.
The other service is name service. The two are orthogonal. Creating an NS record is merely adding records to the zone within the GoDaddy DNS server. It is not modifying or in any way interacting with the glue records that GoDaddy is feeding into the root name servers.
Name service and domain registration are two distinct services.
--
Check out the forum guidelines!
So if I understand that correctly then yes I still need to point the domain to my new nameservers.
All seems to be working now. Can somebody do a DNS lookup and see if the records look right Im not sure personally.
yes it is now correct, but it hasn't fully propagated yet. you see the request is from root and your nameservers instead of godaddy's
7.1% of queries will be returned by 192.5.6.30 (A.GTLD-SERVERS.NET) - answer was not authoritative flirtsnflings.com. 172800 IN NS ns1.flirtsnflings.com. flirtsnflings.com. 172800 IN NS ns2.flirtsnflings.com.
And
7.7% of queries will be returned by 192.5.6.30 (A.GTLD-SERVERS.NET) - answer was not authoritative ns1.flirtsnflings.com. 172800 IN A 94.76.201.163
so this is good now.
to make it simple, for every domain hosted on your server you need to change the ns records at GoDaddy to point to your nameservers ns1.flirtsnflings.com and ns2.flirtsnflings.com.
Again, changing NS records for a domain and registering nameservers are two very different things.
yeah I understand that now.
So when creating a new virtual server in virtualmin, All i need to do is create the virtual server give it the name of the domain and then point my domain in go daddy to my nameservers? Nothing else?
I added joomlaplazza.com as a virtual server and pointed its nameserver to mine and its working but Im still having issues with the mail. It finds the mail.joomlaplazza.com but wont authentic even though i no the password is correct.
your nameservers are okay. Some settings on your machine are not, i.e. hostname shows only ns1
Therefore some stuff breaks. joomlaplazza.com is set up correctly but some settings in the BIND module are not yet correct..
webmin - servers - BIND DNS Server - right pane click at the top on Module config - dropdown choose Zone file options - at Default master server for master zones fill in ns1.flirtsnflings.com - at Serial number style Select Date based - click save
Now: webmin - servers - BIND DNS Server - right pane click Zone defaults.
At Default email address fill in: postmaster@flirtsnflings.com
At Default nameserver for master domains fill in: ns1.flirtsnflings.com Click save.
Now click Miscellaneous Options. Leave all on default except Do full recursive lookups for clients? :selct yes. Click save.
Now click Addresses and Topology and at the right Allow recursive queries from: click listed and fill in
localhost
127.0.0.1
94.76.201.163
Click save.
You have a zone file for flirtsnflings? If so create A records for ns1.flirtsnflings.com and ns2.flirtsnflings.com
Restart BIND.
ok Iv done everything until this part
"You have a zone file for flirtsnflings? If so create A records for ns1.flirtsnflings.com and ns2.flirtsnflings.com
Restart BIND."
Can you explain what you mean here a bit more.
I can see a zone file for .flirtsnflings.com listed as master.
click on the maser zone file for that domain. Click on Address In the field for Name fill in ns1.flirtsnflings.com. (with dot at end) In the field Address fill in 94.76.201.163
Repeat for ns2.flirtsnflings.com. Click save.
Oh and you should set the zone files to Date Based. Thats under Module Config - Zone file options in the dropdown and the the first option at the top.
restart bind
I cant add in ns1 and ns2 then click save I have to put in one then hit create.
so do that for ns1 and ns2? And should the ip address for ns2 be my other ip: 94.76.201.164?
lol yes you create 1 address at the time and certainly with corresponding IP. :) ns2.flirtsnflings.com. with 94.76.201.164
Just making sure, this is fairly complicated stuff for me,
Did you forget to tell me this yesterday?
hehe no I didn't forget but it was late and I thought it was best to take 1 step at the time and let propagation do its thing.
I have a feeling your hostname got un-fixed. Before we take out the hammer, first do the things above and Ill do some shopping in the meantime ;)
Also propagation isn't at 100% yet, but it should mostly work though.
Right done all of what u said and I assume restarting bind is done by hitting apply configuration top right?
it didn't seem to do much
also I did notice in my ssh command prompt that my hostname had changed to just ns1.
Is there anything else I need to do just now. Im going to have to head out soon for a few hours.
Instead of Apply configuration I would prefer to actually restart BIND. On the information page under Status, hit the restart button.
I figured your hostname got un-fixed. You'll need to correct this in the way Ubuntu likes it (look at Joe's comment about it, I use Centos)
Per haps later we need to fix the zone options for your existing domains but lets see what this brings first.
ok
why did it become unstuck in the first place I set this in config files?
I don't know. Im not familiar too much with the way Debian sets its stuff up, but Im sure its something simple.
If you have to go out you could create a temporary webmin user with access to the Virtualmin Virtual Servers, BIND DNS Server, Network Configuration, File Manager modules so i'll take a look and check on that. send it to tech [at][ izicart [dot] com if you want me to have a look.
Sorry had gone by the time you post that last msg but I checked the /ect/hosts file and it has changed to this somehow:
127.0.0.1 andy91 localhost localhost.localdomain
94.76.201.163 ns1 ns1
94.76.201.164 ns2.flirtsnflings.com ns2
If you think it would just be easyer to let you sort out i can create the temp user.
I edited the hosts file as suggested and now postfix has gone down with this error
Failed to query Postfix config command to get the current value of parameter : /usr/sbin/postconf: warning: valid_hostname: invalid character 32(decimal): ns1.flirtsnflings.com /usr/sbin/postconf: fatal: unable to use my own hostname
yeah some minor settings need adjusting. You can create the temp webmin user and Ill look tomorrow. It's the middle of the night here.
Now you are aware of all stuff involved. Understanding will follow. If I've checked and corrected the last issues Ill report back here.
ok done I emailed you the details.
right, it's done.
I needed to adjust the zone settings for the already created domains and some other minor details. Newly created domains will have all the correct settings (as long as your hostname file doesn't change)
You can see it's as perfect as it's gonna get: http://www.intodns.com/joomlaplazza.com
Then I needed to set the hostname for Postfix so that is now also working again. I commented out #myorigin as this usually is a cause for trouble.
I assume you don't use Proftp since no domain is set up to use it.
Now you can fine-tune Apache and secure the server a bit more.
oh yeah I almost forgot. this: "127.0.0.1 andy91 localhost localhost.localdomain" I have changed to "127.0.0.1 localhost.localdomain, localhost" which makes a bit more sense
Hi thanks for that mate!!
Is proftp required for normal ftp usage? Because I noticed that I cant connect to ftp, it just keeps saying connection refused by the server.
Also what should be the out going mail server for the joomlaplazza domain ?
Proftp is the default ftp server but you can use vsftp as well. At the moment proftp is not running and no domain is configured to use it. If you want to use ftp then you have to configure your domains to use it. Else have ssh and sftp (port 22) into the server which is safer.
mail.joomlaplazza.com just as it is now.
I thought ftp was setup automatically on each domain in virtualmin? Yeah I do want ftp working so im going to have to try and configure that.
I have mail.joomlaplazza.com setup as the outgoing server but its not authenticating. I can receive incoming mails but not sent outgoing. It should be set up as the same password right? Any idea whats going on their?
Pages