network profile
| bio | website | |
|---|---|---|
| location | South Africa | |
| age | 37 | |
| visits | member for | 1 year, 1 month |
| seen | May 6 at 12:40 | |
| stats | profile views | 7 |
PHP Programmer / Zend Framework
|
Oct 31 |
comment |
Setting up BIND with wildcard nameserver @Michuelnik I understand that most do it the way you suggest but I know of at least one that does not so it must be possible. It would make our processes a lot simpler if we could get this right. |
|
Oct 31 |
comment |
Setting up BIND with wildcard nameserver I tried various options including the wildcard for the NS records e.g. * IN NS ns1.uafrica.com or *. IN NS ns1.uafrica.com or @ IN NS ns1.uafrica.com or IN NS ns1.uafrica.com but they do not work. With the wildcard when restarting the named service it gives the following error "invalid NS owner name (wildcard)" |
|
Oct 31 |
comment |
Setting up BIND with wildcard nameserver Yes. That would work but only for that specific domain. We need it to work as a wildcard for any domain without having to specify each domain individually. |
|
Oct 31 |
comment |
Setting up BIND with wildcard nameserver We need it to answer for every domain because at the time a domain is registered we do not know what the domain is going to be and we do not want to have to add entries beforehand (and have wait for propagation to happen). |
|
Oct 30 |
comment |
Setting up BIND with wildcard nameserver Thanks for the response. Yes, this configuration is causing a problem in that when trying to register a domain with a .co.za cTLD, the registrar gives an error saying that no ns records exist for the domain. I think the registrar needs to get a specific answer to the query dig @ns1.uafrica.net ubookings.co.za ns which is not happening with this configuration. |
|
Oct 30 |
comment |
How to correctly configure nameservers I think the following is my problem, which I have posted as a seperate issue: serverfault.com/questions/443684/… |
|
Oct 30 |
comment |
How to correctly configure nameservers Thank you for the additional direction. It seems like the problem is related to there being no answer to the ns records. I am still trying to resolve this as I am using a wildcard setup i.e. to get the nameserver to respond the same to every request even if a specific zone has not been created. |
|
Oct 20 |
comment |
How to set up a DNS name server to always resolve to a constant IP address for every request Thanks. I will give it a try. |
|
Oct 20 |
comment |
How to set up a DNS name server to always resolve to a constant IP address for every request Thanks for the response. Another way of putting it is I am looking for a catchall type of thing. So if my nameserver is ns1.mynameserver.com a request to resolve an A record for any domain will always return a certain IP address of say 1.2.3.4 (without any entries having been configured for that specific domain). This way I can point the IP address to a load balancer that always returns a page saying something like "This domain has been registered with myISP and is not yet active" or something like that. Does that make more sense? |
|
Apr 12 |
comment |
Is it possible to set up an additional private edge server on an existing commercial CDN? @SvenW Thanks. If any one knows, please let me know which CDN providers are most likely to offer such capabilities so I can use those as a starting point. |
