DNS Pointers not be...
 
Notifications
Clear all

DNS Pointers not being created for iis service

3 Posts
2 Users
0 Reactions
956 Views
Posts: 237
Topic starter
(@hxkd)
Reputable Member
Joined: 8 years ago

Hi,

Ok running 1.2.0. On iis 7.5 Windows 2008 R2.

When you configure the iis server settings it automatically defines 3 dns records at the bottom which you need to select the shared ip address on each. This has been done so there is an * a www and parent folder record (blank). The below are done on the same server, same hosting plan, just

  1. When the user/website is created using whmcs plugin, only the * record gets created in dns, and a website pointer in the website page ie domainname.co.za is displayed, if you try add a website pointer www.domainname.co.za it says a pointer already exists.
  2. If the user is created manually and the web is created whilst adding a space manually,  then all 3 records get created fine, and the website pointer in the website info page is still domainname.co.za
  3. If the user is added, then a space created without a website and then the website is created, then the * and www pointers are created but not the parentfolder record. Also the website pointer in the website page displays is domainname.co.za.

So it seems there is some issue happening in the scripting depending on how a website is added which only creates certain records, i dont get any errors in eventviewer. Is there not a way to debug the commands as they are executed ?

Also the website pointers in the website page seems to only show domainname.co.za, but not the www.domainname.co.za, if you check the bindings in iis both the bindings are there, but only the root domain pointer is displayed. This is a bit

 

Regards

Keith

2 Replies
Posts: 1457
Admin
(@trobinson)
Noble Member
Joined: 9 years ago

Hello,

The website pointer should only be the www. of the domain (see attached)

 

Do you not see the www. as it shows above? You can see example.com is the main website and www.example.com is created as a pointer.

Can you tell me if the table below is correct for your results? I got a little confused on the use of pointers for DNS.

 

 

Once you can confirm this i will try it aginst our test server to see if i can find the problem.

 

Kind Regards,

 

Trevor Robinson

Reply
Posts: 237
Topic starter
(@hxkd)
Reputable Member
Joined: 8 years ago

Hi, sorry let me clarify and clear up the confusion, i set the web policy to use "www" as the default hostname under policies.

  1. Then when you create the domain when you add a hosting space, you select to create the website with a hostname of "www", the only dns entry inserted into the dns zone is the * dns record, the www and parent records are missing.
  2. If you create the hosting space and don't create the website at the same time, and then add the website manually afterwards using the "hostname of "www" it creates the www, * and parent records fine.
  3. If you use whmcs to create the customer, hosting space and website using the "www" hostname in the config settings in the plan, it only also adds the * record to the dns zone, so I think it is the same as manually doing it, same as in point 1.

Now the weird part, if you do the creation of the site as per all 3 above points, but use the header of "www" as the default hostname it lists it like this.  I would have assumed that if you added the domain, using hostname as "www" the top entry should have been www.ahxtest2.co.za and the bottom one without the "www". But it seems to work in reverse.

If you add the website but dont specify the hostname as "www" you leave it blank it displays it like this.

I then removed the  "www" in the web policy and in the whmcs plan and it creates the sites and applied both the host headers www.xyz.com and xyz.com to the bindings, and it also creates the 3 pointers fine.

The issue here is I know the resellers will setup their packages to provision his hosting plans using the "www" as a host header and then the www and parent dns entries are not going to be created.

I know it can be worked around but its a BIG PITA if you got a few hundred resellers whom all do their own thing, and they wont figure out the issue and will bitch the system is not working properly.

We are using msdns primary and secondary for the dns on these servers.

Reply
Share: