Current File : //proc/self/root/usr/share/webmin/bind8/CHANGELOG
---- Changes since 1.130 ----
A new Module Config option is available to define extra DNS record types for the module to support in a generic way. This allows user who want to create obscure types like NAPTR, KEY and so on to do so.
---- Changes since 1.140 ----
Added an ACL option to limit allowed record types.
Views are now added to the file specified in the Module Config, rather than to named.conf.
The file in Module Config for new views and zones is only used if it is included into named.conf.
---- Changes since 1.150 ----
Added a button for selecting a free IP address when adding Address records, and a Module Config page option for entering IP allocation ranges.
Added basic support for delegation-only zones.
Created two new bind8-lib.pl functions for creating and deleting slave zones, for use by remote callers to avoid transferring large amounts of data via RPC calls.
If the rndc command is installed but does not re-load a zone properly, the ndc command will be attempted as well if possible.
---- Changes since 1.160 ----
Added a Module Config option to control whether or not the PID file is under the chroot directory.
---- Changes since 1.180 ----
Added a new display mode for the zones list - an expandable tree categorized by parent domain.
---- Changes since 1.190 ----
Slave zones now display the last date on which they were transferred.
When using date-based SOAs, the starting number for the serial can be specified in the module configuration.
Added button for re-downloading the root zone nameservers, which may occasionally change.
---- Changes since 1.200 ----
Basic information about all domains is now kept in a separate cache file, which can be read faster than the primary named.conf file. This speeds up the zone list and editing of records on systems that have a large number of domains.
More than one slave server to add new master zones to can now be defined, and zones will be added, deleted and applied on all at once. When a slave is added, existing master zones can also be converted to new slave zones on it.
Multiple master, slave or forward zones can now be created at once from a batch file, using a new link on the module's index page.
When a list view is used for zones, several can now be selected at once and deleted using a single button.
---- Changes since 1.210 ----
Added a new page for setting up RNDC on BIND version 9, so that individual zones can be reloaded.
Updated the Control Interface Options to be more consistent with the rest of the module.
Added support for easily creating SPF records. Even though these are really TXT records, they now appear as a separate type in this module.
---- Changes since 1.220 ----
Moved the option for the default nameserver for new master domains to the Zone Defaults page, where it is more obvious.
---- Changes since 1.240 ----
Added a Module Config option for Unix time serial numbers.
Multiple records in a zone can be deleted at once using checkboxes in the records list.
---- Changes since 1.250 ----
When deleting a zone, the .log or .jnl file created by BIND for dynamic DNS updates is also removed.
Added an icon for manually editing the BIND master configuration file.
Reverse IPs are updated even when the forward record names are not fully canonicalized.
Added an ACL option to allow a Webmin user to apply the BIND configuration, but not stop or start the server.
---- Changes since 1.260 ----
When adding a cluster slave DNS server, you can specify that slave zones created locally should also be created on the slave too, with the same settings.
Added a Module Config option to not read or display records in a zone by default, which speeds up the process of adding records to very large zones. Thanks to Walgreens for sponsoring this feature.
When deleting multiple Address records, their corresponding reverse records can be deleted as well.
Cluster slave DNS servers can have an alternative hostname specified, for use in the NS records on the master when a new zone is added.
Added a field on the Addresses and Topology page for controlling which clients can make recursive queries.
When an automatic filename is chosen for a zone added to a view, the view name is included in order to avoid clashes.
---- Changes since 1.270 ----
Added support for the TLS protocol in SRV records.
Added select all / invert links to slave servers list.
---- Changes since 1.300 ----
In the template records file, $IP and $DOM will be substituted with the IP address and domain name when creating a new master zone.
---- Changes since 1.310 ----
Added an option to the master zone creation page to create PTR records for for template A records.
---- Changes since 1.320 ----
Added a button on the main page for updating the values of records in multiple domains at once. Useful for mass IP address changes.
---- Changes since 1.330 ----
Allowed views are now enforced when adding multiple zones from a batch file.
---- Changes since 1.340 ----
Updated the Edit Record form to use ui-lib.pl, for easier theming.
Fixed a bug that can occur when deleting multiple DNS records at once, causing the wrong ones to be removed.
---- Changes since 1.360 ----
Added a button to the main page for adding a record with the same name and value to multiple domains at once.
---- Changes since 1.370 ----
Multiple zones can be deleted and updated when using the icons view.
---- Changes since 1.380 ----
Added buttons for freezing and un-freezing a master zone, for use on systems that also use dynamic DNS. Thanks to Cl�ment V�ret for submitting this patch.
When adding a remote slave zone, the IPs of all other slaves and the master are included in the master IPs list.
---- Changes since 1.390 ----
BIND on Windows can now be configured using this module.
Mass record creation can now add records for the domain name (by entering @ as the name), as records that already exist.
---- Changes since 1.400 ----
Keys in ACL sections are no long mangled by Webmin. This means that each IP or key must be entered on a separate line in the Access Control Lists page.
---- Changes since 1.410 ----
Corrected parsing of records in zone files with no names, which inherit from the previous record.
Spaces are now allowed in Host Information records.
---- Changes since 1.420 ----
The default TTL for multiple zones can now be changed on the Update Records in Zones page.
When adding a cluster slave server, multiple views can be entered to have slave zones created in all of them.
Record names or values entered like ns.foo.com in the domain foo.com automatically have a . added to make them absolute as the user presumably expected, rather than being converted to ns.foo.com.foo.com.
Update serial number (by default) when editing records manually.
Try downloading root zone files from the IP for rs.internic.net if the hostname cannot be resolved, to avoid catch-22 problem.
Access control lists are now automatically re-ordered to handle dependencies.
When Webmin is not automatically converting records to canonical format for editing, display the canonical name on the Edit Record page.
When adding a cluster slave server, allow zones to be created in the same view on the slave as on the master.
Added a button to the Edit Master Zone page for checking records with the named-checkzone command.
---- Changes since 1.430 ----
Don't pass the -g flag to BIND version 9 when starting without an init script.
Converted all forms to use the Webmin UI library, for a more consistent look and easier theming.
Moved buttons for deleting, moving and converting zones up to the page shown when you click on a zone name.
Switched to the new root zone file available from Internic.
Restrictions that apply to all zones in a view (such as allowed IPs for transfers and queries) can now be set on the Edit Client View page.
Made the Find Free IPs page visible, for finding addresses in a master zone that are not currently used.
Added a field to limit concurrent outgoing zone transfers and incoming transfers per nameserver to the Forwarding and Transfers page.
Ignore tailing dots in zone names in named.conf.
---- Changes since 1.440 ----
Moved the apply, stop and start buttons to the top-right corner of every page, so that you don't have to return all the way to the module's main page to apply configuration changes.
Zones can now be signed with DNSSEC, using one or two keys. This can be done automatically at master zone creation time, or later for existing zones. Signatures can also be removed or re-generated at any time. Zones with a key-signing and zone key can have their zone key automatically regenated on a regular interval.
Added the DNSSEC Verification page for configuring BIND to validate signatures on other zones, and to use DLV until the root zone is signed.
SPF records can now be added to or updated in multiple zones at once.
Added an icon to the main page for checking the whole BIND configuration including zone files, with the named-checkconf command.
Added a Module Config option to prevent inclusion of other slave's IP addresses in the master IP list for remote slaves.
---- Changes since 1.450 ----
Fixed the 'Directory for DNSSEC keys' option on the Module Config page so that it is actually used.
SPF records longer than 255 bytes are automatically split into separate fields in the underlying TXT record.
---- Changes since 1.460 ----
When adding a master zone with automatically created slaves, add an also-notify block to the master configuration to update the slaves.
---- Changes since 1.470 ----
Added mass record change and creation buttons to the zone search results page.
Made the manual config file editor textboxes full-width.
Fixed a bug that cause blocks like sortlist not be parsed properly, and possible cause Webmin to corrupt other parts of the named.conf file.
Redirect and explanation modifiers can be viewed and edited in SPF records.
Added a Module Config option for additional master IP addresses for remote slave zones.
If nscd is running when BIND is restarted or a zone is applied, it will be signalled to re-read DNS caches too.
---- Changes since 1.480 ----
When all DNS records in a zone are shown, the Type column can be clicked on to sort them.
---- Changes since 1.490 ----
Root zone records files are now included in Webmin backups.
---- Changes since 1.500 ----
Added new NSEC3 algorithms for DNSSEC.
Changed the default DNSSEC algorithm from DSA to the stronger RSASHA1.
---- Changes since 1.510 ----
On Linux systems, /dev/urandom is used for generating entropy for DNSSEC.
---- Changes since 1.520 ----
Added the Delete Records In Selected button to the main page, for removing the same record in multiple domains at once.
---- Changes since 1.530 ----
The default view for new zones can now be set via an option on the Module Config page.
When adding cluster slave servers, their IPs are added to the also-notify and allow-transfer blocks of each domain added to the slave.
IPv6 addresses can now be used for remote nameservers in slave and delegation zones.
---- Changes since 1.540 ----
Added the Test Zone Transfer button to the slave zone page, to check if zone transfers are possible or not.
---- Changes since 1.550 ----
Links for editing and deleting records now using the record name instead of an index, which makes editing more reliable if records are also being updated by dynamic DNS or some other tool.
When a zone is reloaded, it is now frozed first and then thawed afterwards with the rndc command, to better support dynamic DNS.
---- Changes since 1.580 ----
The source IP and port for zone transfers can now be specific on the Addresses and Topology page.
Added support for zone signing using the DNSSEC-Tools suite, thanks to a patch from Suresh Krishnaswamy.
---- Changes since 1.600 ----
Changed all links to zones to use the zone name instead of an index, to prevent incorrect modification during concurrent access to the module.
---- Changes since 1.620 ----
Added a module configuration option to use the SPF type for Sender Permitted From records.
---- Changes since 1.660 ----
Added a warning if the chroot directory that Webmin thinks BIND is using looks wrong.
Slave zone files in raw format can now be displayed by Webmin.
---- Changes since 1.720 ----
Added support for NSEC3PARAM records.
---- Changes since 1.730 ----
Added support for editing DMARC records, which are specially encoded TXT records for defining the response to SPF and DKIM violations.
---- Changes since 1.770 ----
Automatic creation and deletion of reverse records in partial delegation zones now works the same as in full reverse zones.
---- Changes since 1.810 ----
Added support for editing TLSA (SSL Certificate) records.
---- Changes since 1.830 ----
Added support for editing SSHFP (SSH Public Key) records.
---- Changes since 1.880 ----
Before a zone is updated, BIND will be told to freeze it and thaw afterwards. This ensures that dynamic updates are preserved.
---- Changes since 1.930 ----
Added support for CAA records.
¿Qué es la limpieza dental de perros? - Clínica veterinaria


Es la eliminación del sarro y la placa adherida a la superficie de los dientes mediante un equipo de ultrasonidos que garantiza la integridad de las piezas dentales a la vez que elimina en profundidad cualquier resto de suciedad.

A continuación se procede al pulido de los dientes mediante una fresa especial que elimina la placa bacteriana y devuelve a los dientes el aspecto sano que deben tener.

Una vez terminado todo el proceso, se mantiene al perro en observación hasta que se despierta de la anestesia, bajo la atenta supervisión de un veterinario.

¿Cada cuánto tiempo tengo que hacerle una limpieza dental a mi perro?

A partir de cierta edad, los perros pueden necesitar una limpieza dental anual o bianual. Depende de cada caso. En líneas generales, puede decirse que los perros de razas pequeñas suelen acumular más sarro y suelen necesitar una atención mayor en cuanto a higiene dental.


Riesgos de una mala higiene


Los riesgos más evidentes de una mala higiene dental en los perros son los siguientes:

  • Cuando la acumulación de sarro no se trata, se puede producir una inflamación y retracción de las encías que puede descalzar el diente y provocar caídas.
  • Mal aliento (halitosis).
  • Sarro perros
  • Puede ir a más
  • Las bacterias de la placa pueden trasladarse a través del torrente circulatorio a órganos vitales como el corazón ocasionando problemas de endocarditis en las válvulas. Las bacterias pueden incluso acantonarse en huesos (La osteomielitis es la infección ósea, tanto cortical como medular) provocando mucho dolor y una artritis séptica).

¿Cómo se forma el sarro?

El sarro es la calcificación de la placa dental. Los restos de alimentos, junto con las bacterias presentes en la boca, van a formar la placa bacteriana o placa dental. Si la placa no se retira, al mezclarse con la saliva y los minerales presentes en ella, reaccionará formando una costra. La placa se calcifica y se forma el sarro.

El sarro, cuando se forma, es de color blanquecino pero a medida que pasa el tiempo se va poniendo amarillo y luego marrón.

Síntomas de una pobre higiene dental
La señal más obvia de una mala salud dental canina es el mal aliento.

Sin embargo, a veces no es tan fácil de detectar
Y hay perros que no se dejan abrir la boca por su dueño. Por ejemplo…

Recientemente nos trajeron a la clínica a un perro que parpadeaba de un ojo y decía su dueño que le picaba un lado de la cara. Tenía molestias y dificultad para comer, lo que había llevado a sus dueños a comprarle comida blanda (que suele ser un poco más cara y llevar más contenido en grasa) durante medio año. Después de una exploración oftalmológica, nos dimos cuenta de que el ojo tenía una úlcera en la córnea probablemente de rascarse . Además, el canto lateral del ojo estaba inflamado. Tenía lo que en humanos llamamos flemón pero como era un perro de pelo largo, no se le notaba a simple vista. Al abrirle la boca nos llamó la atención el ver una muela llena de sarro. Le realizamos una radiografía y encontramos una fístula que llegaba hasta la parte inferior del ojo.

Le tuvimos que extraer la muela. Tras esto, el ojo se curó completamente con unos colirios y una lentilla protectora de úlcera. Afortunadamente, la úlcera no profundizó y no perforó el ojo. Ahora el perro come perfectamente a pesar de haber perdido una muela.

¿Cómo mantener la higiene dental de tu perro?
Hay varias maneras de prevenir problemas derivados de la salud dental de tu perro.

Limpiezas de dientes en casa
Es recomendable limpiar los dientes de tu perro semanal o diariamente si se puede. Existe una gran variedad de productos que se pueden utilizar:

Pastas de dientes.
Cepillos de dientes o dedales para el dedo índice, que hacen más fácil la limpieza.
Colutorios para echar en agua de bebida o directamente sobre el diente en líquido o en spray.

En la Clínica Tus Veterinarios enseñamos a nuestros clientes a tomar el hábito de limpiar los dientes de sus perros desde que son cachorros. Esto responde a nuestro compromiso con la prevención de enfermedades caninas.

Hoy en día tenemos muchos clientes que limpian los dientes todos los días a su mascota, y como resultado, se ahorran el dinero de hacer limpiezas dentales profesionales y consiguen una mejor salud de su perro.


Limpiezas dentales profesionales de perros y gatos

Recomendamos hacer una limpieza dental especializada anualmente. La realizamos con un aparato de ultrasonidos que utiliza agua para quitar el sarro. Después, procedemos a pulir los dientes con un cepillo de alta velocidad y una pasta especial. Hacemos esto para proteger el esmalte.

La frecuencia de limpiezas dentales necesaria varía mucho entre razas. En general, las razas grandes tienen buena calidad de esmalte, por lo que no necesitan hacerlo tan a menudo e incluso pueden pasarse la vida sin requerir una limpieza. Sin embargo, razas pequeñas como el Yorkshire o el Maltés, deben hacérselas todos los años desde cachorros si se quiere conservar sus piezas dentales.

Otro factor fundamental es la calidad del pienso. Algunas marcas han diseñado croquetas que limpian la superficie del diente y de la muela al masticarse.

Ultrasonido para perros

¿Se necesita anestesia para las limpiezas dentales de perros y gatos?

La limpieza dental en perros no es una técnica que pueda practicarse sin anestesia general , aunque hay veces que los propietarios no quieren anestesiar y si tiene poco sarro y el perro es muy bueno se puede intentar…… , pero no se va a poder pulir ni acceder a todas la zona de la boca …. Además los limpiadores dentales van a irrigar agua y hay riesgo de aspiración a vías respiratorias si no se realiza una anestesia correcta con intubación traqueal . En resumen , sin anestesia no se va hacer una correcta limpieza dental.

Tampoco sirve la sedación ya que necesitamos que el animal esté totalmente quieto, y el veterinario tenga un acceso completo a todas sus piezas dentales y encías.

Alimentos para la limpieza dental

Hay que tener cierto cuidado a la hora de comprar determinados alimentos porque no todos son saludables. Algunos tienen demasiado contenido graso, que en exceso puede causar problemas cardiovasculares y obesidad.

Los mejores alimentos para los dientes son aquellos que están elaborados por empresas farmacéuticas y llevan componentes químicos con tratamientos específicos para el diente del perro. Esto implica no solo limpieza a través de la acción mecánica de morder sino también un tratamiento antibacteriano para prevenir el sarro.

Conclusión

Si eres como la mayoría de dueños, por falta de tiempo , es probable que no estés prestando la suficiente atención a la limpieza dental de tu perro. Por eso te animamos a que comiences a limpiar los dientes de tu perro y consideres atender a su higiene bucal con frecuencia.

Estas simples medidas pueden conllevar a que tu perro tenga una vida más larga y mucho más saludable.

Si te resulta imposible introducir un cepillo de dientes a tu perro en la boca, pásate con él por clínica Tus Veterinarios y te explicamos cómo hacerlo.

Necesitas hacer una limpieza dental profesional a tu mascota?
Llámanos al 622575274 o contacta con nosotros

Deja un comentario

Tu dirección de correo electrónico no será publicada. Los campos obligatorios están marcados con *

¡Hola!