19

Yes this is possible. All you need to do is follow the same advice you were for a pod specification, but rather than applying it to a YAML file for pods, you apply it to a YAML file for a deployment. For example, if you are already running a deployment you can edit the current deployment by issuing the following command. $ kubectl edit deployment ...


14

In today's world, I do not recommend creating new zones with arbitrary top level domains, as these might make it into "official dns" at any point in time. I personally would favor the subdomain delegation scenario, as it seems to be fitting what you try to do. (Consolidate but give control to engineering) Maybe you can even find a web-front-end for MS DNS ...


14

First and foremost, make sure you own the domain.tld you plan on using (mit.edu). Even if this never connects to the internet, that's not the point. There are huge benefits to having a hierarchy of dns that at least somewhat matches the org. I've only seen this done when there is someone/people to manage that department in terms of IT support. This is in ...


14

This line from the log indicates the problem: Jun 15 06:12:39 pizza.yoderdev.com unbound[1947]: [1947:0] debug: skip addr on the donotquery list ip4 127.0.0.1 port 53530 (len 1 Unbound by default refuses to send any DNS queries to localhost. To enable it to query localhost, set the do-not-query-localhost to no in the server-section of the Unbound ...


14

If you have access to create your certificates for that server I suggest you create a certificate that includes alternate names that the server may be known as. In that way the browser will automatically resolve the correct name. From https://blogs.msdn.microsoft.com/varunm/2013/06/18/bind-multiple-sites-on-same-ip-address-and-port-in-ssl/ SAN ...


12

/etc/resolv.conf: Lists nameservers that are used by your host for DNS resolution. If you are using DHCP, this file is automatically populated with DNS record issued by DHCP server. /etc/hosts/: It is just a static lookup method for resolution. /etc/nsswitch.conf: It defined order of resolution. Who should it consult first for resolution, a DNS or a host ...


11

I had to add "bind-interfaces" to the config file, so that interface and listen-address had the desired effect. E.g.: listen-address=127.0.0.1 interface=lo bind-interfaces This will have the desired effect of listening only on localhost. I was running into issues, since I was running a public dns (that resolves just my own domains) on the public ip of the ...


11

We see from your output that IP address was changed from 12.43.168.248 to 12.43.168.105. This is not a big problem if you use DHCP. But this is very uncommon behavior if you use DHCP on Windows Server - it keeps leasing info by default, so you have a big chance that your DHCP pool is over.


10

Is it considered normal practice to add an A record for example.com at my DNS provider pointing to the private ip (192.168.2.13), so that development.example.com can resolve to my machine inside my private network? That will certainly work, but it's not best practice as it opens the door for a bit of information leakage about your private network. ...


10

You should basically never, ever allow non-secure updates. Personally I don't even like that the DNS server even allows you to turn off secure updates. This allows anyone on your network (like a hacker) to register DNS records with no Active Directory authentication required. This would allow the attacker to "spoof" a DNS name on your network and redirect ...


10

In the world of DNS website.test.company.com and www.website.test.company.com are two completely different URLs. Whether you are running Windows or Linux and your webserver you need to make you sure have either an alias for www.website.test.company.com or a binding in IIS for www.website.test.company.com You also want to make sure you have a CNAME record ...


10

I think most likely a DHCP issue. Possibly you have multiple servers/devices with DHCP role leasing IP's with same network range (Maybe a Router has DHCP role as well as Windows Server), your servers/printers don't have static IP or reservation or your DHCP server leases IP addresses for too short a time. Does the event log on DHCP server have any entries ...


9

host-record=example.com,1.2.3.4 The dnsmasq man page says: --host-record=<name>[,<name>....][<IPv4-address>],[<IPv6-address>] Add A, AAAA and PTR records to the DNS. This adds one or more names to the DNS with associated IPv4 (A) and IPv6 (AAAA) records. A name may appear in more than one host-record and therefore be ...


9

You shouldn't have a reason to forward to other AD servers, as DNS should be replicating between them already. The only reason I can think of for this would be if you wanted only one DNS server to be the one querying the internet for non-authoritative FQDNs. Usually the forwarders (used to resolve non-authoritative lookups) are set to external DNS servers ...


9

Here is a partly-redacted screen capture of two A records on one of our Windows Server 2008 DNS servers: As you can see, there are two different names in two different A records with the same IP address in both records. I just created this image in the last ten minutes. There are several other examples all over our Windows DNS servers of this. The admin ...


8

It works as expected. The incorrect assumption here is that all names should have NS records. Instead, the set of nameservers is defined on a per zone basis, with NS records at the zone apex only. Eg, if you have example.com and have not delegated any subdomains elsewhere, then there are no further NS records anywhere under example.com. If you delegate foo....


7

Never rely on whether your app will be internal or external. Always develop as though the audience of the app will be outside your control (because it is). Go with ENV.APPNAME.DOMAIN.TLD With www. as the alias for "production".


7

Zone files on slave DNS servers often do not (and should not) have information to this hidden master DNS server. They can have A records in their zone files to point to this hidden DNS master server. The server is called "hidden" not because no one can ever know about it, but because it's not listed anywhere using NS records so clients can't query them. ...


7

There is no difference between private (RFC1918) and public IP addresses except that the former are not routable on the Internet and the latter are. Your DNS zones can point to both these private and public IP addresses as to the DNS — and to routers and other devices — there is no difference between private and public IP addresses. Your SSL/TLS certificates ...


6

There's no problem doing that - in fact, one of the major consumer router manufacturers used to provide a domain name which had an A record pointing to 192.168.0.1 (though I can no longer find any documentation of this). However, if you will only need this DNS record on your local network, you should run a local DNSmasq or TinyDNS as suggested by @EEAA ...


6

No, you should not add RFC1918 IP addresses to public glue records. There are a few reasons for this: If your internal hosts use a DNS server outside the LAN where the RFC1918-addressed authoritative nameservers are, a SERVFAIL will result for obvious reasons It adds garbage to the set of glue records It will have unintended consequences if a resolver in a ...


6

It's perfectly valid to have multiple A records pointing to the same IP. Reverse lookup has nothing to do with it; as that would a) be in a separate zone and b) would be using PTR records. Certificates are also irrelevant here.


5

Not knowing how your environment is set up and what your goals are I'll risk suggesting that you shouldn't have your DC/DNS servers using any other DC/DNS servers as forwarders. The only scenario where I've seen internal DNS servers using other internal DNS servers as forwarders is when the security policy restricts outbound DNS traffic to a few secured DNS ...


5

> DNS Servers . . . . . . . . . . . : 192.168.5.7 10.10.0.21 8.8.8.8 Your tertiary DNS server is one of Google's. Why are you configuring this on the clients instead of configuring a forwarder on your internal DNS servers? When the problem occurs, the machine is probably ...


5

Creating a private hosted zone in Route 53 essentially applies a "hook" in the DNS resolver for your VPC so that queries for that domain are routed directly to the assigned Route 53 nameservers instead of being resolved normally by traversing down starting at the global root servers. In light of that, I suppose it makes sense for the system to consider a ...


5

The simplest way forward would be to use mDNS to do "ad-hoc" DNS resolution amongst the machines in the same subnet. This is, basically, as simple as installing avahi-daemon and libnss-mdns (Debian package names; adjust as appropriate) and making sure your firewall isn't blocking 5353/udp. This will cover both forward and reverse DNS entries, and create ...


5

How to do DNS redirect without DNS server? (I'm assuming you mean CNAMEs, because DNS doesn't redirect) By definition, you can't. Unless you use hosts file hackery. Also note that while you can CNAME a hostname wiki to mycompany.atlassian.net you cannot use DNS to "redirect" wiki to mycompany.atlassian.net/wiki. What's the problem? The /wiki at the end. ...


5

The problem You don't own the domain name mynas.local, so of course Let's Encrypt won't sign a certificate saying that you own that domain. If they signed such certificates, browsers would very soon stop trusting Let's Encrypt. Instead what you need to do is to use your own domain name to access the NAS regardless of where you access it from. This is not ...


5

Thanks @joeqwerty. It was necessary to edit named.conf on the DNS server in network A. zone "network-b.mycompany.com" { type forward; forward only; forwarders { 10.17.0.1; }; // The DNS server's address in network B }; Source: Conditional DNS forwarding with named on Linux


5

Why not setup forwarding for the zone for domain.com and create a new zone for a subdomain of domain.com for which the local name server is authoritative? My example uses example.com instead of domain.com ... 192.168.33.0/24 +--------------------------+ | ...


Only top voted, non community-wiki answers of a minimum length are eligible