network profile
| bio | website | twitter.com/#!/WebdevCol |
|---|---|---|
| location | Leeds, United Kingdom | |
| age | 33 | |
| visits | member for | 1 year, 2 months |
| seen | Jan 6 at 18:43 | |
| stats | profile views | 0 |
Web Developer, all flavours.
|
Mar 1 |
awarded | Supporter |
|
Mar 1 |
awarded | Scholar |
|
Mar 1 |
accepted | setting up subdomain in IIS/DNS - possible incorrect subdomain structure |
|
Mar 1 |
comment |
setting up subdomain in IIS/DNS - possible incorrect subdomain structure Seems to be working now, and turns out it probably was a nameserver issue (DOH), however i'll mark this as the accepted answer because of your suggestions/help, Thanks |
|
Mar 1 |
comment |
setting up subdomain in IIS/DNS - possible incorrect subdomain structure Thanks eric, yes they are pointing to an external server. (aa.66) works, however i've just noticed that it wasn't set on my zoneedit account, and the 1&1 nameservers were set to prioritise my zoneedit NS before 1&1 NS.(setup before 1&1 allowed editing of DNS records), so i've updated the nameservers, and added aa.77 to the zoneedit as well. leaving them to propogate and then will see. |
|
Feb 29 |
comment |
setting up subdomain in IIS/DNS - possible incorrect subdomain structure I've added the A records as such: Hostname:aa.77 Pointsto:0.0.0.0 and Hostname:77 Pointsto:0.0.0.0, and 24-48 hours later, it's still giving me the same error message. Does the order inside the DNS list matter? should 77 appear before aa.77? |
|
Feb 28 |
comment |
setting up subdomain in IIS/DNS - possible incorrect subdomain structure Thanks for this, i'll give it a try. Its an external DNS server hosted by one and one. |
|
Feb 28 |
awarded | Student |
|
Feb 27 |
awarded | Editor |
|
Feb 27 |
awarded | Analytical |
|
Feb 27 |
revised |
setting up subdomain in IIS/DNS - possible incorrect subdomain structure added more information |
|
Feb 27 |
asked | setting up subdomain in IIS/DNS - possible incorrect subdomain structure |
|
Feb 27 |
awarded | Autobiographer |
